Change SQL Server Connector to import datetime data with greater than 1 second granularity

jimsteph

SQL Server's Time and DateTime fields store data to the millisecond (Time datatypes are accurate to 100 nanoseconds). However, the connectors truncate those data types to the nearest second. I put in a ticket when I found this — I really do need to keep the milliseconds when importing — but was told it's working as designed, and the workaround is to cast those fields as text when importing, then cast them back later in every ETL that uses them with the timestamp() function. This is inelegant and annoying.

My request is that either the SQL Server connectors be rewritten to import the actual data down to the millisecond, or (better) that a mechanism is added to control the precision of the import for time and datetime fields that defaults to 1 second to avoid breaking existing flows.