Hi,
I just encountered an unexpected problem with the MSSQL_SPATIAL writer.
I originally set a manual command ("exec some-stored-procedure-with-arguments") to define a spatial index and more, which err'ed because there was no primary index on the relevant table. That's fine and understandable.
As I really didn't needed a spatial index on the specific table anyway, I just switched the dropdown "Spatial Index Type" to "None", and reran the translation.
But the translation still failed in the same place, while trying to execute the now deselected and unwanted command.
It seems like the command was still present, and FME tried to execute it as such, even though the setup stated it shouldn't. This I believe to be buggy behaviour, the overall choice should not be overridden like that.
Cheers
Lars I.