Menu
I'm starting to get involved in quite a bit of ETL work a my current job, and everyone seems to be pretty partial to SSIS. I'm struggling trying to do the most trivial transformations through BI studio that would usually equate to a couple foreach loops with a pinch of LINQ. Im not sure of the use cases or users this tool would be useful for, and will probably convince management that I can do without. What's the best way to make my case, or if there are any recommendations for better tooling, that would be appreciated as well.
907
SSIS is a great tool, but you have to grasp underlying concepts first. It allows you to focus on the ETL process, instead of programming and debugging your code. There is a learning curve. Take a look at Microsoft Project Real examples and see what would be foreach loop equivalent for something like that.
Even though SSIS packages are built inside of Visual Studio, when you are in the context of a Script Task or Script Component, you are actually coding in the VSTA environment that is, in fact, a mini-project within the package.
SSIS Developer is a very trending career profile of the year 2020. The year 2019 witnessed unprecedented growth in the demand of SSIS Developers. The overall demand for SSIS developers rose from 17% in 2018 to 24% in 2019. This has led to a lot of people to consider this SSIS profile as their career option.
Time and Hard Work In fact, learning SSIS will take more time than learning almost any other technology. Why? Integration Services is a software development platform for moving data. Learning it well requires understanding both database technology and software development.
I don't know SSIS, besides reading up some of the basics. Also like you I'm very comfortable with LINQ, and could quickly write code to push around and transform data.
But what if the table has 4 gigs of data? Do you think your LINQ code is going to handle that gracefully? It could be handled, but not easily, especially if there are a lot of tables cross-referencing each other. A naive LINQ implementation would try to load everything into memory and crash.
Another justification is because your coworkers are strong with SSIS. Any solution you give the company built on SSIS will be more valuable to the company than LINQ, since other people can pick it up and fix or extend it.
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
