Replies: 4 comments
-
Hi @jbfbell, 1+ vote from me. I have to use MS SQL server for work and found the normalisation with DBT (Destination V1) to be very very slow as it uses views. It might be due to the sync is based on cursors and not CDC. I hope that Typing and Deduping with Destination V2 would be much faster, but I'm not an expert. |
Beta Was this translation helpful? Give feedback.
-
Support for MSSQL is the most important factor why I evaluate Airbyte. In my usecase I'm fetching data from ERP system to ecommerce. |
Beta Was this translation helpful? Give feedback.
-
+1 on this. |
Beta Was this translation helpful? Give feedback.
-
+1 - this would be extremely helpful |
Beta Was this translation helpful? Give feedback.
-
We removed "normalization" from Destination MSSQL. Normalization was a process which would extract data from the raw json format and cast the data into tables with the appropriate types. For other destinations, we implemented Typing and Deduping to replace normalization and we will bring typing and deduplication to MSSQL if there is sufficient interest
The purpose of this discussion is to gauge interest in bringing this functionality back to MSSQL.
Without typing and deduping, you would need to integrate another tool, such as dbt to accomplish the same result. While integrating another tool gives you greater customization over the data format, it comes with additional operational overhead.
Should Airbyte bring Typing and Deduping to MSSQL?
Beta Was this translation helpful? Give feedback.
All reactions