• Why don't folks use structured storage files more, rather than storing packages in SQL Server? Putting packages in structured storage files makes moving packages around much easier (just a simple file copy) and it makes it possible to "version control" the packages too, if you want to do that. Editing the packages is a bit of a hassle (opening them to edit them, that is), but otherwise it seems to make it much easier to deal with.

    We've got several packages for a couple of different systems that I've moved to structured storage files. And, after modifying the packages to allow them to be dynamically configured (via INI files), we've got one set of packages that can be used in three separate environments (development, staging, production). Structured storage files in combination with dynamic configuration solves many problems with deployment (except where Analysis Services is concerned, but that's a separate problem).