March 27, 2008 at 11:08 am
What have been the limitations that you have encountered while using SSIS 2005? This can range from connectivity to a RDBMS other than MSSQL to extraordinary circumstances that have not yet even been documented in a FAQ somewhere.
It is my intention to glean from the SSIS development community their unique situations that have hit a "brick wall" through no fault of there own but due to a limitation of the application of SSIS?
Please contribute freely and at will.
-Mike DiRenzo
March 27, 2008 at 1:26 pm
I have used it extensively and run into issues, but nothing that I would call a "brick wall".
For instance, it is not compatible with older Oracle OLEDB drivers - so I have had to install newer ones. The lookup component does not work with SQL 7 (oddly enough), so I have had to use script components or merge joins. The UI is a bit flakey in visual studio - but I can live with that.
It is terrible at things it is not made to do (email a user and wait for a response before continuing is something I have seen people do), but it is pretty solid for a second generation ETL product.
March 27, 2008 at 2:58 pm
Lot of minor areas that I have wished that could be more polished and more ready for prime time.
For instance, in DTS you could double lick to select mytbl_imp from next line, but SSIS is a total mess in that regard.
IF OBJECT_ID ( 'mytbl_imp' ) IS NOT NULL TRUNCATE TABLE mytbl_imp
Flat file editor has very little supports for real ETL work. It doesn’t give you the capability to sample/preview the last part of the file. No scale to let you know, say third column is from position 5 to 11.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply