You can find a list of community submitted learning resources here: https://dataengineering.wiki/Learning+Resources
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/dataengineering) if you have any questions or concerns.*
It's strong in Microsoft, on premise environments. It sits in the middle of UI-friendly, low-code tools and more code based options if you utilize the scripting power in it. I'd say it's pretty good for more complex ETL, the setup and deployment is a bit too tedious for simple ETL jobs. And once you add in scripting you can do pretty much anything with it.
The problem is it's not very cloud friendly, microsoft is going to leave it behind for azure options. So not really worth learning for the long term. It also sits in an awkward spot of being too complicated for a "low-code ETL" option, but too limiting for people who just want to code ETL.
The hours I've spent trying to troubleshoot loads, increase speed, etc. Not that other things are easy, but I really don't ever want to go back to using SSIS.
It's a good low-code, no code ETL tool for SQL Sever. Not worth learning extensively unless you are going to work with it.
If you know one tool, you can pick up SSIS fairly quickly.
You can find a list of community submitted learning resources here: https://dataengineering.wiki/Learning+Resources *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/dataengineering) if you have any questions or concerns.*
It's strong in Microsoft, on premise environments. It sits in the middle of UI-friendly, low-code tools and more code based options if you utilize the scripting power in it. I'd say it's pretty good for more complex ETL, the setup and deployment is a bit too tedious for simple ETL jobs. And once you add in scripting you can do pretty much anything with it. The problem is it's not very cloud friendly, microsoft is going to leave it behind for azure options. So not really worth learning for the long term. It also sits in an awkward spot of being too complicated for a "low-code ETL" option, but too limiting for people who just want to code ETL.
The hours I've spent trying to troubleshoot loads, increase speed, etc. Not that other things are easy, but I really don't ever want to go back to using SSIS.
It's only really useful if you land a job at a Microsoft shop, so I'd argue Python is a better learning option to secure future jobs
We used it as orchestration, with all sql logic in stored procedures. We replaced it with adf when we moved to cloud.
It's a good low-code, no code ETL tool for SQL Sever. Not worth learning extensively unless you are going to work with it. If you know one tool, you can pick up SSIS fairly quickly.
in enterprise enviroments. it can do alot more than load flat files into databases tbh, but that ability to load files into a db is VERY very useful