I didn’t write that it’s missing and I don’t see fault in SSIS only
-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 !
Not if you're following best practices (i.e. use configurations or apply environmental-specific settings from the command-line). For anyone reading this, be aware that you should NEVER EVER be required to edit packages when moving them through environments.
-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 ?
Fair point. Although I can't envisage any situation where 2 developers have to work on a single data-flow. That's akin to 2 developers working on a stored procedure concurrently and I wouldn't generally allow that. I'm not saying that's correct though, if you have a different approach then I have no issue with that.
But I strongly believe that not allowing 2 people to edit a data-flow simultaneously is a GOOD thing. Having said that, not allowing 2 people to work on a package simultaneously is a BAD thing.
-Debug and error handling SSIS has this
Yes but I prefer try catch statements with nested functionality
Fair enough. Each to their own.
-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.
Errr OK. Not really sure I understand this one. Are you saying you want to version each task? If so then yes, I think that's a very fair criticism. SSIS doesn't handle that very well at all.
-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
You say "how can admin do it without modification packages " That's completely true but exactly the same applies to using stored procedures so I don't really understand this one. Sorry.