|
I'd rather rewrite Oracle Networking in Notepad so I can use Oracle Loader, than SSIS. Even if Microsoft's SQL Server Integration Services is by far the fastest data mover in the world (as they claim), I just don't like it.
I think it's stupid to get rid of relative paths. Simply stating the name of a file (in the same or current folder) no longer works, because, as with DTS, packages can be stored directly inside SQL Server, rather than in the file system. If the latter, paths must be hard coded in some form.
I think making a new system environment variable with the path and file name to your XML configuration file is retardedly stupid. Even worse than storing your config (with connection strings) in a database.
I don't trust Integration Services's ability to manage a slowly changing dimension, and I don't like having to use a "wizard" to do this.
I don't like that stored procedures must not only execute, but finish sending the TDS until SSIS begins to work.
I don't like the parent package variable concept.
I don't like the row by row paradigm in the data flow.
I don't like that data has to move from the server to whatever machine is running SSIS and back to the target server (which may or may not be the source). This is hugely inefficient.
I could go on griping forever, but I wonder how other people are using SSIS, and what they think of it? I'm using 2005, by the way.
|
