Skip to main content

After upgrade to 2023.1.2 FME Form from FME Desktop 2022.2 Microsoft SQL Server Non Spatial Writer start writing empty attributes for all text fields but Datetime field still populating. Have anyone encountered this issue before? I tried changing TYPE to text, varchar_max, char, non of these works on FME Form 2023.1.2

I have replaced that writer, replaced the workspace with brand new canvas, still no luck.

 

But when I run the same exact workspace in FME Desktop 2022.2 the table populates fine.

 

To make it even more confusing, within the same workspace I have another SQL Server writer but it just goes to another table, both version are able to populate all records.Ssms_DtsnfKSLm6Something interesting I saw on the log for 2023.1.2 version is that before it showed 11 record written to the table, 120 attributes were truncated. (not sure why?), but in 2022.2 version there's no warning on this issue.

Ssms_SqE2w5jMSHI also attached log files from both versions.

I've come across something similar with nvarchar(max) fields, the solution was to disable Bulk Insert on the writer.


I've come across something similar with nvarchar(max) fields, the solution was to disable Bulk Insert on the writer.

Thank you for you suggestion! Unfortunately Bulk insert is set to No already for me and it still not working >,<


Thank you for you suggestion! Unfortunately Bulk insert is set to No already for me and it still not working >,<

There's some more discussion in this thread which is related https://community.safe.com/s/question/0D54Q00009mVZN1SAO/fme-inserts-null-value-into-nvarcharmax-columns-in-sql-server-using-microsoft-sql-server-nonspatial-format-after-the-latest-fme-upgrade . By the comments I think it's still a bit of an issue.


Thank you for you suggestion! Unfortunately Bulk insert is set to No already for me and it still not working >,<

Thank you so much for this article! i'll try this suggestion :D


Thank you for you suggestion! Unfortunately Bulk insert is set to No already for me and it still not working >,<

I have tested this and confirm that it is now working by changing writer to MSSQ Non-Spatial JDBC and new database connection. Thank you so much!!


Reply