In FME 2016 there were a possibility to set how geometries would be stored in the MSSQL writer.

For instance, Arcs could be stroked with a setting within the writer when stored in the table, without using the Arcstroker-transformer.

However, in recent version this isn´t possible any more.

My problem:

I have a set of polygons in a MSSQL-database table (let's call it table 1) that was written thru the 2016 MSSQL-writer.

(The original data is stored in a different database (oracle) which i use to update and create new data)

I then use FME-server to write all the data (edited, new, untouched ) from Oracle to a different table i MSSQL (let's call it table 2) each night .

The MSSQL database then comapers the areas of the original table (1) and the comparison table (2) which I'm writing data to each night.

I do this check to see if I got any new, deleted or changed geometries (area comparison) before posting them to the "correct" MSSQL-Table (1).

When I changed to a newer version of FME-server the arcs in the polygons isn't stroked in the MSSQL writer, so I receive a message from the database which says that every polygon that contains an arc has to be updated, because the areas differs.

I've tried to use arcstroker, that dosen´t stroke the arcs the same way as MSSQL 2016 writer = goes to "update" even if they havn´t been updated.

I've also tried to use geometrycorecerer to separate arcs from polylines, stroked the arcs and then built the polygons back together. But it only results in the same sequence of events. The stroking of arcs dosen´t match the former MSSQL-writer.

Is it possible to replicate the type of stroking that occured in the 2016 MSSQL writer in any way?