SQLExecutor with Custom SQL schema failed warnings by Microsoft SQL Server Spatial Reader

@virtualcitymatt Thanks for the link and I will have a look at it and implement it if that solves the problem.

Unfortunately there is a reason why I am trying to avoid the use of  writer. Actually two.

1. It needs an ArcGIS Pro installation on the FME Server (Flow) machine to use ArcGIS SDE reader/writers
2. the speed that the Arc SDE reader/writers offer is not up to par, considering we are querying a database. Reading with the SQLExecutor, altering a bit the schema of the data and writing them out to a dgn… about 500.000 features takes about 5 minutes and is way faster then the ArcGIS SDE reader. Now I hope we can achieve similar results for the writer.

Hi @virtualcitymatt,

adding OUTPUT Inserted.OBJECTID does return the objectid value, but it does not avoid the warnings about Microsoft  SQL Server Spatial Reader, coming from the SQLExecutor.

Now the warning simply got the output line added:

Microsoft SQL Server Spatial Reader: Getting Custom SQL schema failed. Custom SQL query 'INSERT
    INTO
    building (OBJECTID,SHAPE)
    OUTPUT Inserted.OBJECTID
VALUES (27, geometry::STGeomFromWKB(here is of course the binary, 25832))' may execute in an unexpected manner. Make sure all columns are named (any ambiguous columns, e.g. GEOM.STBuffer(1), must have an AS clause). If there is an ORDER BY clause, either remove it or add a TOP clause. If this warning is generated in a SQLCreator or SQLExecutor, you can avoid it by picking Data Features in the Features to Read field

Ahh interesting - too bad. I wonder if the issue is because of the format is spatial - So the reader is expecting a geometry

What happens if you try and use non-spatial version of the format. In this case the non spatial wont expect any geometry on the output. 

Another similar issue here:

SQLCreator warnings and geometry not read when using order by with SQL Server | Community (safe.com)

I was having the same issue. I tried everything until I did something absolutely non related then the error was gone, I removed “ ; ” (semicolon) from the end of my T-SQL statement: 

This was my code with semicolon:

SELECT i.[name] AS DatabaseName

,(i.[size]/128.0) AS FileSizeInMB

,((i.[size]/128.0) - CAST(FILEPROPERTY(i.[name],'SpaceUsed') AS int)/128.0) AS EmptySpaceInMB

FROM sys.database_files as i;

This is my new code (without semicolon):

SELECT i.[name] AS DatabaseName

,(i.[size]/128.0) AS FileSizeInMB

,((i.[size]/128.0) - CAST(FILEPROPERTY(i.[name],'SpaceUsed') AS int)/128.0) AS EmptySpaceInMB

FROM sys.database_files as i