I have an SSIS package that uses an Environment variable to hold the connection string for the local SSISConfiguration table. This works properly on my local machine. However, when I import the package to Integration Services(through
SSMS) it reads the environment variable from the local machine and not the server it is deployed to. If I log on to the server remotely and do the same process it uses the the correct environment varible... (SQL Server 2005)
Is there a way to deploy the package to the server and get it to use the correct Env variable without having to log-in to the server and import it? Let me know if anyone is looking for additional information. Thanks!
View Complete Post