I have a SSIS package that I need to move to a production server. Currently the package is working fine on the development environment. There are two connection in the package to SQL Servers, both of which are development machines. When we move the package to production we need to our database team to enter the new source and destination during installation as the servers are not the same and I do not know the login information ahead of time. The package does not appear to prompt during installation for any connection information even when I left the save password unchecked. Please tell me how to get the installation ask for these connection. Thanks

Create a XML-Configurationfile and configure both Connections. Create a DeploymentManifest for deloying. Then you can write the new Connectionstrings in and the package works fine on Production, too.

I do not know the production database login information. I am in a development group who only has access to development servers. I know what the address of the production servers are but I do not have the login information to pre-configure an XML file. The production information needs to be entered during deployment by the database team.

The configuration files can be XML files. During development, you would fill those files with the development server location and credentials. During deployment, you would give your database team the packages and the configuration files. The database team would alter the server connection string and credentials inside the configuration files. Talk to me now on