How To Support Multiple SQL Server Package Configurations in SSIS
I have several applications that use SSIS packages and I want to be able to store all the configurations together in a single table when I deploy. When a package executes I need a way of specifying the "application" and having SSIS automatically handle the package configuration based on the application.
2012-08-21
2,727 reads


When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?