Microsoft SQL Server 2005/2008 SSIS are oversized
- by Ice
In this case i'm old style and loved 'my fathers DTS' from SQL 2000.
Most of the cases i have to import a flatfile into a table. In a second step i use some procedures (with the new MERGE-Statement) to process the imported content.
For Export, i define a export-table and populate it with a store proc (containing a MERGE-Statement) and in a second step the content will be exported to a flat file.
In some cases there is no flat file because there is annother sql-server or in rare cases an ODBC-Connection to a sybase or similar.
What do you think?
When it comes to complex ETL-Stuff the SSIS may be the right tool...but i haven't seen such a case yet.