I have a dilemma of sharing Snowflake data with several on-prem SQL server.
The question is if I should use CData to replicate data by batch from Snowflake to SQL server, or if I can create a Linked Server using CData driver to avoid data movement.
I understand there would be performance implications of each approach. However, I am curious to hear your thoughts.
That’s actually a very good question and lot of customers actually have the same doubts. What we are talking about is comparing two different approaches of solving the same problem: 1.) Replicate Data from Snowflake to SQL Server (or ETL) 2.) Linked Server Approach (or Data Virtualization)
In the first approach, you are actually lifting and shifting the data, however in the second approach, you are just making the data available in SQL Server without having to copy it.
There are definitely tradeoffs in both the approaches and there is no right answer to which approach is better. However, once you understand the tradeoffs, it is easier for you to make a decision depending on your environment.
Thanks for sharing the whitepaper. However, I still have question about CData product for connecting on-prem SQL server to a Snowflake database.
Is CData Connect Cloud the only choice for this? Although this might be a good solution, this would require me to go through internal InfoSec review and network suuport.
Is there another way? Does CData have a driver that works with SQL Server Linked Server?
How about we setup a meeting to discuss this further? I will have someone from our team reach out to you to setup a meeting and we can answer any questions you might have.