Here I would like to post a topic where the most of the environments face problem with SSIS Variable and connection managers..Etc when moving a SSIS package from one environment to another (Ex: Dev to Production). I have seen environments where the Package Configurations were maintained and also some not maintained. I personally like to maintain the Package Configurations. It is very time consuming and sometimes false databases and servers to be pointed when Package Configurations are not maintained. Whether a package is small or complex, but still maintaining Package Configurations is make your work easy.
Type | Description |
| XML configuration file | An XML file contains the configurations. The XML file can include multiple configurations. |
| Environment variable | An environment variable contains the configuration. |
| Registry entry | A registry entry contains the configuration. |
| Parent package variable | A variable in the package contains the configuration. This configuration type is typically used to update properties in child packages. |
| SQL Server table | A table in a SQL Server database contains the configuration. The table can include multiple configurations. |
No comments:
Post a Comment