I didn’t write that it’s missing and I don’t see fault in SSIS only
Let’s evaluate
-Forward changes to test environment If this means its possible to promote code to different
environments then SSIS has this too.
Promote code to different environments should freeze projects but when you want
test package you must write\reconfigure connection – potential errors !
-Multi user development SSIS has this
It’s for me freezing code for some task . We need to implement a little complex data flow task
we have two programmers how we could divide jobs for them ?
-Debug and error handling SSIS has this
Yes but I prefer try catch statements with nested functionality
-Versioning SSIS has this (versioning of packages). And unless there's some sort of new feature
that I don't know about there is no versioning of stored procs within the database engine
But if you can use not commercial concurrent versioning system it’s maybe problem delegate
code because xml include some binary data.
-Logic for concurrent loading/ incidental loading Not quite sure what this means but with SSIS
its possible to load multiple tables concurrently.
In real life ETL is very complex and has very dependent task. When something
is going wrong it’s needed quick find the errors and reprocess flow.
In some situations the best choice will be ignore error data, how can admin do it without modification
packages ? Why to the @#!#!! when you run package in agent job you can only see it as one atomic job. I want to say that SSIS package without more flexibly control loading tool (based on metadata) it’s condemned only on run in dubug mode 😉