Curious about the future of data-driven systems? Join our Data Engineering roundtable and learn how to build scalable data platforms.
Data Engineering: The industry has come a long way from organizing unstructured data to adopting today's modern data pipelines. See how.
Stats
| Reputation: | 281 |
| Pageviews: | 126.7K |
| Articles: | 3 |
| Comments: | 2 |
Comments
Jan 05, 2017 · Tim Spann
Hi Toni,
thank you for your insight. I don't want to suggest using only pure SQL, As you said - there are many cases when it is not possible. This articles idea was just to show that there are situations in which writing pure SQL is giving a big performance boost.
On the other hand it is possible to merge data from two different servers. It is also a common case when people write ETL's istead of pure T-SQL, while T-SQL is noticeably better. But as you said - in some cases, for example loading data between two different database brands, you have to think about ETL. However even in such cases, one should consider writing for example "View" on source instead of transforming data in ETL.
As you said, there a lot of possibilities.
All the best,
Mateusz
Dec 29, 2016 · Mateusz Komendołowicz
Always happy to discuss practices with you. :)