August 15, 2011 at 6:54 am
I documented how to deploy an SSIS package for myself. The first thing I do is create a config file which gets stored in a folder on the remote system I use. I then set the deployment properties for my package (setting CreateDeploymentUtility to TRUE, setting the DeploymentOutputPath to the same remote folder I saved the configuration file in). I then build my package. When it's done building, I go to that remote folder and there's the .dtsx and the .SSISDeploymentManifest file, but the .dtsConfig file is no longer there (I verified it was there before I built the project). I don't recall this happening in the past. What am I doing wrong?
November 8, 2011 at 12:47 pm
The deployment folder is "cleared out" on every build. When you use the Package Configurations Organizer to make a new configuration, specify the location of the xml file to be different than your deployment path.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply