Skip to main content
  • EN

Hello,

I came across this warning:


“ 2024-10-08 15:14:19|  14.7|  0.0|WARN  |Microsoft SQL Server Non-Spatial Writer: Failed to parse `Date' from attribute value ` 19810101' for column `InstallDate'
2024-10-08 15:14:19|  14.7|  0.0|WARN  |Microsoft SQL Server Non-Spatial Writer: Failed to parse ' 19810101' as a datetime value. For FME datetime syntax, please see http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/! “

 

As you can see, FME is trying to write to a SQL database, but is failing due to syntax error. 

This results in all of the items that have this syntax error NOT BEING WRITTEN to the database, and those which do match the syntax being written. In my specific case this resulted in 25 features out of 20,000 not being written, as this was a warning rather than an error this was missed for several months, causing quite a few issues. 

Can we get an option to cancel transactions or throw an actual error in the case data is not being written in its full extent?


Thanks

I’ve been hit by this one too (combined with an attribute name that seemed to imply it was a numerical field… “numberoftracks”…. turned out the possible values were “one”, “two” and “lots”)

Yup. I‘ve been bitten by this one too. In general you’re never 100% sure if stuff was (partly) written or not, when you get these kinds of warnings. So then the state of your data becomes completely unclear, and it takes time to check the integrity afterwards…

@redgeographics : How about “diameter” on a pipeline? You’d think that be a numerical value. Some of the actual values I found: “2.5 inch”, “2,5 inch”, “20 centimeter”, “45”, “twee decimeter”….. 

But I must admit that “lots” made me laugh 😄

 

@redgeographics : How about “diameter” on a pipeline? You’d think that be a numerical value. Some of the actual values I found: “2.5 inch”, “2,5 inch”, “20 centimeter”, “45”, “twee decimeter”….. 

But I must admit that “lots” made me laugh 😄

Oooof, that is just nasty…

I must admit I did exaggerate for comedy effect, the actual values were “Enkelspoor”, “Dubbelspoor” and “Meervoudig”. End result was that my database with Top10NL data had no railways...

Try to extrude a pipeline into a 3D object by a value of “1.2 feet”….

 

“End result was that my database with Top10NL data had no railways”

And that is what gets me. If you do not carefully dig through the logfile, you’ll miss the fact that some of the data wasn’t actually written, when the translation log says that it was succesful… Been working with FME for a good 12 years or so now, and this still trips me up now and then...

I learned to be triggered by differences in featurecounts because of this.

New→Open

Once again I’ve been hit by this, my SQL table writer was set to automatic, and chose tinyint for my datatype, one of my values to be written to this table was 5000 (invalid number for tinyint), hence my table had 57 items ‘written’, but my actual sql table had only 51 rows of data. without scrolling through 170 lines of warnings, this is missed. 

This is a serious issue, please offer an option to create an error if there is a parsing warning such as:

2025-07-17 14:15:40|   0.5|  0.0|WARN  |Microsoft SQL Server Non-Spatial Writer: Failed to parse `Unsigned TinyInt' from attribute value `5000' for column `How many kilolitres (kL) of liquid waste was generated? '

Community Stats

31,756
Posts
120,637
Replies
39,380
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.