Change SQL Server Connector to import datetime data with greater than 1 second granularity
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.
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 303 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 104 SQL DataFlows
- 640 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 767 Beast Mode
- 70 App Studio
- 43 Variables
- 715 Automate
- 185 Apps
- 460 APIs & Domo Developer
- 56 Workflows
- 14 DomoAI
- 39 Predict
- 16 Jupyter Workspaces
- 23 R & Python Tiles
- 402 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 134 Manage
- 131 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive