SQLSERVER Reader type generates unnecessary warnings

I can just add that this is a fairly common request with our clients: they want to get rid of warnings that aren’t important to their process, so that “real” warnings get better visibility in the Flow jobs overview.

So far I’ve only managed to remove certain warnings by introducing transformers specifically to get rid of them (e.g. CoordinateSystemRemover, Decelerator, BulkAttributeRemover, etc...) but I find it unsightly and it complexifies the workspace for no good reason.

It would be fantastic if there was a way to ignore known warnings (using wildcards?) on a per-workspace basis.

Agreed. It would improve my jobs-dashboard tremendously. I know in my dashboard I could get the logfile, parse it, and filter out these warnings, but that would slow the dashboard down...

To be honest, I don’t even understand why this particular one (“does not include a spatial column. Geometry will not be read”) has to be a warning at all. Information maybe, but even then: I wrote that SQL statement that the transformer has to execute myself, so I know there’s no geometry in the select. Why should that be a warning? It’s my own doing! It makes no sense to me in this case...

Fully agree. 

I recently had a case where the Clipper gave a warning about being unable to use 0 for tolerance and that it had calculated a different value. The problem was that this older version of the Clipper didn’t even have the tolerance setting! The solution was to update the Clipper and make sure the tolerance was set to automatic, and just hope that all the new settings that were introduced didn’t change the result.

There’s lots more that have cropped up from 2024 onwards

“Resetting a database that is still referenced”

“No query delimiter specified; SQL will be treated as a single statement. To specify the delimiter token, write FME_SQL_DELIMITER <token> as the first line of SQL text”

Warning message: Resetting a database that is still referenced. | Community

Oh yes, the no-query-delimiter one. I’ve got some quite complicated sql’s, using CTE’s and unions - that one always crops up with those kinds of statements. 

Never encountered the resettng-database one though, at least not that I remember.

But the spatial column one only started showing after the introduction of the single SQLSERVER reader-type, so that is fairly recent. The no-query-delimiter I’ve seen for a looong time, if memory serves me right I’ve already encountered that one when still using 2014.