SSIS - How to deploy package on production server

Hello there,

I created a SSIS project in Visual Studio 2010 and MSSQL 2012.Now I created some packages which is working fine on my machine(development). Now I want to move these packages on the production server so I can run these packages there. How can I transfer/move my packages to my production server.My production server has sql server 2008. hope it will work there.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian CroweDatabase AdministratorCommented:
You should be able to right-click on the project in the solution explorer and select deploy.  This will bring up a wizard which will prompt you for the target instance and some other information.
zolfAuthor Commented:
Brian, Thanks for your comments. But,I want to deploy it on another machine which is at my client side.
Vikas GargAssociate Principal EngineerCommented:

Right click on the project properties

set the create deployment utility to true

Build your project.

This will create manifest file

Go to the Package path and then go to \bin\deployment folder.Double click the Integration Services Deployment Manifest file.

Double click on that file to the destination machine where you want to deploy and you will enter in the deployment wizard which will guide you toward deployment.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SolarWinds® Network Configuration Manager (NCM)

SolarWinds® Network Configuration Manager brings structure and peace of mind to configuration management. Bulk config deployment, automatic backups, change detection, vulnerability assessments, and config change templates reduce the time needed for repetitive tasks.

zolfAuthor Commented:
Vikas, Thanks for your comments.

I will create the manifest file on the dev machine. Till here it is clear. Now, do i need to copy the manifest file on the production server or what,here it is not clear.Can you please elaborate.
Vikas GargAssociate Principal EngineerCommented:

Manifest file will be created to the \bin\deployment folder where your package is.

Now you need to copy that manifest file to the machine where you want to deploy.

If production server is different then development you have to copy that to production server
zolfAuthor Commented:
If production server is different then development you have to copy that to production server

Yes the production server is different at my client side.  So where do I copy this manifest file on the cleint machine and how do I deploy it on their machine
Vikas GargAssociate Principal EngineerCommented:
You can copy to any location in Production server.

And you can deploy using deployment wizard.
zolfAuthor Commented:
Do i need to copy only the manifest file or the full bin folder to the client side
zolfAuthor Commented:
On my development machine the manifest file is shown in the screenshot. DO I just copy the manifest file on the client machine or the full product folder.

zolfAuthor Commented:
zolfAuthor Commented:
Another thing, is the database name and the credential differs on the Client machine. How does manifest file take that into consideration. Please help, it is my first deployiment
zolfAuthor Commented:
OK, I managed to use the manifest file to export the package from my machien to the client server. On the client machine I open SSIS via Management Studio and under MSDB I see my 2 packages there. Now when I try to run the package on the client server I get this error.see shot

zolfAuthor Commented:
The problem I know is the sql server credential, the credential of the user on my machine is different from the client. I was able to change the database name in the Connection Managers option of Execute Package Utility but not the password. How can I change the password.
zolfAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.