title: Should programmers use SSIS, and if so, why?
body: <p>As a .NET developer, for what reasons should I prefer SSIS packages over writing code? We have <em>a ton</em> of packages in production where I currently work, and they're a nightmare to both "write" (perhaps draw?) and maintain. Each package looks like a bowl of multicolored spaghetti with C# and VB.NET scripts mixed in at the points where the abstractions break down. To figure out what each "Execute SQL Task" or "Foreach Loop" does, I have to double click the damned thing and browse through a tree of literal values and expressions, scattered across multiple tabs.</p>
  
  <p>I'm open minded, so I'd like to know if any other <em>good developers</em> find SSIS more productive than just writing some code. If you do find SSIS more productive, please tell me why.</p>