deploy pacakge - what files have to go?

I'm getting ready to deploy my SSIS packages to a real server (woohoo) after testing on my local SQL box. What files have to be deployed to the SQL server? I'm creating a folder for each package (easier for these guys to maintain when my contract is up). Does only the .dtsx and .dtsConfig file go or is there any other files that have to be copied over to the SQL server?

Only the dtsx files need to go. You can deploy individually or you can set the create deployment utility as a Project Property and then just double click the manifest to deploy all of them at once. You shouldn't have to manually copy any files.

|||

Ok, even though I have a .dtsconfig file defined for them, that doesn't have to go to the servers?

As for the .dtsx file, I see one in the Bin folder of my project and one outside of the bin folder which one goes or does the deploy utility grab the correct one?

|||

In the Deploymet folder there should be a file with the extension .SSISDeploymentManifest. Double click on that. It will deploy the files from the Deployment folder.

If you don't have a Deployment folder, right click on the project and choose properties.

In the properties page, click on the Deployment Utility entry (middle one) and change create deployment utility to True.

|||

Ok, thanks, I'll look into it. This is the first for this for me, so. .

|||

If you want to include the configuration settings from the .dtsconfig file then you should deploy it. I am 99.9 % certain that you want to include it.

The deploy utility will grab the correct .dtsx file.

|||

From my experience (not very much though ), its easier to do a xcopy than going through the process of creating deployment package modifying the manifest etc., That way you wont miss copying the config files also.

Its just my thought.

Thanks