As for trying to use SSIS, it doesn't help that one of the books I own on SSIS says things like:
"By the time that SQL Server 2000 was released, DTS had a strong following of DBAs and developers. Microsoft included in the release new features like the Dynamic Properties task to help you dynamically alter the package at runtime. It also had extended logging and broke a transformation into many phases, called the multiphase data pump. Usability studies still showed that at this point developers had to create elaborate scripts to extend DTS to do what they wanted. For example, if you wanted DTS to conditionally load data based on the existence of a file, you would have to use the ActiveX Script task and VBScript to dynamically do this. The problem here was that most DBAs didn't have this type of scripting experience.
It sort of sucks as a developer when you open up a book you bought on Amazon and the first thing it says is a red flag that indicates you are not its primary audience. In other words, I read this paragraph as, "DBAs aren't software engineers, and need hand holding." I think that lets the reader down, and is a cop out, and the authors were completely lazy in their justification. The harder question to answer is: What sort of scripts did DBAs have to write, and why were they so time consuming and are they actually very uniform and fit canned patterns that deserve automation? That question isn't insulting to DBAs and annoying to developers.
They are talking about DTS, the predecessor of SSIS. The line about DBAs not having scripting experience is about ActiveX and VBScript. I thinks that is largely correct. Most DBAs are well versed in TSQL and maybe Powershell, but those other two languages are something totally else.
SSIS is intended as more of an Enterprise ETL solution. So DTS should actually never be compared with SSIS.
Developers (in the sense of coding applications in .NET or another language) can certainly work with SSIS and they are in familiar territory since the development is done in Visual Studio, but SSIS requires another way of thinking. It is mostly a graphical tool, instead of purely coding.
Now, the answer the hard question 🙂
DBAs, the core audience of DTS, had to write ActiveX and VBScript scripts - languages that a certain part of those DBAs were not comfortable with - in order to do certain tasks in DTS. These tasks can now easily be done in SSIS without too much coding effort.
I think those paragraph was intended to convince people to abandon DTS and to embrace SSIS.