Over here, Oren posted a list of 15 issues with SSIS. Some are founded, most are not. Read on for more:
Below are each of Oren’s points with my response:
You have to understand though, that this isn’t .Net. SSIS has many components/engines at work that obtaining the correct error isn’t always at the heart of the SSIS engine. It could be a database error. It could be an ADO error. Whatever it may be, I agree, some are cryptic, but I’ve generally been able to diagnose my errors. And if there is an error I don’t know about, I contact the community and finally Microsoft through product support.
The fact these are random should banish this item from your “SSIS 15 Faults” list.
Keeping track of what it shouldn’t:
Never had this happen. NEVER. NEVER, NEVER, NEVER, NEVER. Did I make my point? Come over to the forums for help if this is happening and we can help troubleshoot.
Sorry excuse for deployment:
I don’t understand any of the points made here. Deploying to a server has never been a problem. It is in the manual that metadata cannot change between databases/tables. So if you’re moving to an environment that has its metadata different than another, you need to reconcile that first. Also, you aren’t using “select * from table” or selecting tables in the drop down box in the OLE DB sources are you? NEVER do that. Always select the specific columns you need (even if it’s all of them) manually so that DBAs can add fields to the table without causing metadata changes.
Security? Who needs that:
An SSIS package doesn’t need sysadmin rights to execute. Period.
UI Formatting instructions:
Ah, well, what would you say if the SSIS dev team decided to make SSIS packages binary? THEN WHAT? At least you have an XML file that can be parsed.
No thought about version control:
Agreed. Version control is flaky.
Bad configuration scheme:
I don’t understand this. Please elaborate.
Random configuration scheme:
B.S. – I beg to differ.
Yes! The UI needs improvement.
Lack of extensibility:
Really? Darren, Jay care to comment? There are plenty of API guys that know what they’re doing and can help you out if you just ask.
Is your Oracle example an SSIS problem, or the Oracle driver’s problem?????????
Hard to debug:
Within reason, yes, this is true. You now know about using the watch box.
The missing basics:
UPSERT? Really? http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1211340&SiteID=1