I'm not familiar with SQL Server but could it be the table you're trying to write to is reprojecting the data as it's coming in? As in SQL Server itself is doing the reprojection to match the SRID defined for the table? what happens if you try and create a 100% new table.

The other thing (probably more likely) is that maybe the geometry column is define as Geography as opposed to Geometry.

https://learn.microsoft.com/en-us/sql/relational-databases/spatial/spatial-data-sql-server?view=sql-server-ver16

Thanks for your reply. I do have it set to Geometry type and it is dropping and recreating the table each time. Maybe there is a different transformer required here.

Well you should be able to check the Setting on the writer and specify the correct coordinate system you want. You should also be able to inspect the data directly before the SQLServer writer and check the coordinate System of the features. The coordinate System Information is in the Feature Information window.

If The writer is set to the coordinate system you want and the data going in are in the coordinate system you want then the issue is most likely happening during export to SQLServer - there could be some warnigns or info in the log file which may be helpful here

It looks like I have it working now. I used the PROJProjector transformer, with Automatic Transformation, 7899 as my source coordinate system and 7855 as my destination coordinate system., and 7855 as the Output Coordinate System Tag. In the writer it is set to Drop and Create for table handling, and spatial type is Geometry. I've also changed the spatial column field name. It must have been something in this combination that got it working, or perhaps there was one thing I clearly missed before.

Thanks again.

Josh