I have raised a suggestion on Connect for a change to the current behaviour of SSIS templates. Here are the details:
Description:
When you use template packages you run into problems. Mainly because all of the packages created from the same template have the same properties. The worst case being that the ID of the packages are all the same.
This is bad - very very bad.
At the moment a SSIS template isn't really a template per se. Its just a package that happens to reside in a particular place. If it were a proper template then many of the properties of that package would get changed as if the package were getting created for the first time.
Proposed Solution:
I would like a new method on the Application class (http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.application_members.aspx) or perhaps a new overload of the Application.LoadPackage method (http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.application.loadpackage.aspx) that opens an existing package but also does a few extra things:
1) Loops over the executables collection and recreates all of the ID properties.
2) Changes the ID of the package.
3) Requires the user to specify a new name for the package.
4) Change CreatorName, CreatorComputer, CreationDate properties accordingly.
5) Resets the Description property to some default value.
6) Resets Major/Minor/Build version numbers to 1.0.0
7) Sets PackageType property to an appropriate value (e.g. If a template designed in Yukon were to get opened in katmai then current behaviour is that PackageType=DTSDesigner90.
If you think that this is a good idea then please click-though here and vote. The current behaviour, whilst not being a bug, is not intuitive and needs changing.
Thanks
-Jamie
Posted to SSIS (RSS feed)