Hi,
I currently have a SQL Server database product with which I would like to distribute some packages for customers to use for importing and other processes. Obviously these package must run using connections and file locations that would not match those when developed.
My current strategy is:
- Provide a dtsConfig file which has entries for database connection string and an email server connections string. This is set to Indirect XML Configuration where customer would be required to create an Environmental Variable that contains the name and path to the dtsConfig file
- For files location and other values, I have taken a data-driven approach, e.g. a set of tables contain the information the package needs. During testing this seem,s to work quite well for my needs.
- All tasks and connections managers have the DelayValidation set to True
Does anyone know if this would be a viable strategy for distributing packages to 3rd parties? If not, any suggestion or pointer to reading materials.
Thanks
Steve
I currently have a SQL Server database product with which I would like to distribute some packages for customers to use for importing and other processes. Obviously these package must run using connections and file locations that would not match those when developed.
My current strategy is:
- Provide a dtsConfig file which has entries for database connection string and an email server connections string. This is set to Indirect XML Configuration where customer would be required to create an Environmental Variable that contains the name and path to the dtsConfig file
- For files location and other values, I have taken a data-driven approach, e.g. a set of tables contain the information the package needs. During testing this seem,s to work quite well for my needs.
- All tasks and connections managers have the DelayValidation set to True
Does anyone know if this would be a viable strategy for distributing packages to 3rd parties? If not, any suggestion or pointer to reading materials.
Thanks
Steve
Thanks Steve