Skip to main content
Archived

MS SQL parameter to ignore 'alleged' datetime issues

Related products:Integrations

FME dates are irritating when working with MS SQL as I can handle dates more effectively in MS SQL.

I have a workbench that processes 100+ CSV files, each file has a different structure so I process each file dynamically.

Dates can be formatted as 19 Sep 2011 13:09:00 or 19 Sep 2011 13:09 which MS SQL is happy enough with but FME isn't.


At the moment I use a Python script to load the full file and do a regex replace to resolve the FME date issue.

It's really bad that FME simply nullifies any date issue so it is quite possible we are unaware of issues.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings