Question

Microsoft SQL Server Non-Spatial error handling

  • 3 January 2019
  • 1 reply
  • 1 view

I have noticed in FME 2018.0 and 2019b that the Microsoft SQL Server Non-Spatial writer only raises a warning when a feature is not written due to (for example) NULL value constraints.

Personally I think that an error should be raised in any situation where a feature is not written to the database.

Despite the warning, the workspace continuous normally and the feature even shows up in the features written summary.


1 reply

I have made a quick solution in the form of a startup-script:

Reply