March 8, 2010 at 8:24 am
I have been developing a package that calls other packages and for development I use file connections to the packages I want to call. When I deploy this I would like the packages to be stored in SQL I have not seen a parameter in the Exec Package task that references the connection type. Is there a way to change this with configs??
March 8, 2010 at 9:10 am
I did a quick little bit of research and it looks like the difference in configuration from a file source to a SQL source is largely that a package name (and associated "path") are specificed for a SQL connection.
A "path" takes the form of "\Maintenance Plans\SystemMaintenancePackage" where \Maintenance Plans\ is the path and SystemMaintenancePackage is the package name.
The file source explicitly specifies a package so the package name in the exec package is blank.
You can see this for yourself by doing this..
Create 2 EXEC package tasks
Set one up as a file source and the other as a sql source.
Look at their properties.. Particularly "PackageName"
CEWII
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply