ssis package deployment

Question

I have deployed a package from my local machine to dev server.

If i want to make any changes to the deployed package on dev server (say edit the query), then i can do it on dev server or do i need to deploy the package again after making the required changes on my local machine.

Please advice.Thanks

Answer 1

I would suggest making the change on your local machine and then deploy to the dev server separately.  Ideally you would use source control with your package so that you keep all versions of the package.

Any scenario I can picture where you edit a package on the dev server invlolves pulling the package into an SSIS project and pushing that package back to where you have depoyed your package on the dev server.

---

Russel Loski, MCT, MCITP Business Intelligence Developer and Database Developer 2008

Answer 2

can we deploy same package twice on dev server?

Answer 3

and i have two package in one solution.When i deploy on dev server by using manifest file, both the package gets deployed.

Is there any way only one package gets deployed OR i have to make two seprate solution for each package?

Answer 4

can we deploy same package twice on dev server?

yes

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 5

and i have two package in one solution.When i deploy on dev server by using manifest file, both the package gets deployed.

Is there any way only one package gets deployed OR i have to make two seprate solution for each package?

In your case i feel its better to re depoly everything again

but you can send then the changed package and give then the instruction on how to over write the old one.

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 6

So, when we redeploy the package,will the old package still be on dev server or only the new redeployed package will be there.

Answer 7

What ever you do IF you deploy to the same loacation it will ask you to overwrite or not ,

it will be a simple yes or no or cancel deployment.

Or you maybe deploying to a folder so it will be

Overwrite file , Yes , No , Cancel

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 8

I would create a BAT file employing the DTUtil in there. 1st I would delete the old package like

DTUTIL /SQL <PACKAGENAME> /DELETE /SourceS <ServerName>

This is because sometimes the "refresh" does not work well, especially in SSIS 2005.

The next step is to install the updated package. To do so add the 2nd line:

DTUTIL /FILE <DRIVE:\FOLDERNAME\PACKAGENAME.DTSX> /COPY SQL;<PACKAGENAME> /QUIET

The above it to take the package from the file system and place into the MSDB.

After the aforesaid is done you end up with the old package gone.

---

Arthur My Blog

Answer 9

This thing applies both for file system dployment and sql server deployment

Answer 10

This thing applies both for file system dployment and sql server deployment

yes

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 11

One thing more, do we have an option to deploy particular package in the solution (if solution have , say five packages).

OR all the packages will get deployed.

Answer 12

I would create a BAT file employing the DTUtil in there. 1st I would delete the old package like

DTUTIL /SQL <PACKAGENAME> /DELETE /SourceS <ServerName>

This is because sometimes the "refresh" does not work well, especially in SSIS 2005.

The next step is to install the updated package. To do so add the 2nd line:

DTUTIL /FILE <DRIVE:\FOLDERNAME\PACKAGENAME.DTSX> /COPY SQL;<PACKAGENAME> /QUIET

The above it to take the package from the file system and place into the MSDB.

After the aforesaid is done you end up with the old package gone.

---

Arthur My Blog

I think that you deserve to get the point as an answer

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 13

Thank you Nik, likewise, your input is as always invaluable!

---

Arthur My Blog

Answer 14

One thing more, do we have an option to deploy particular package in the solution (if solution have , say five packages).

OR all the packages will get deployed.

s i had mentioned before you can deploy any package at any time, you dont have to deploy all of the packages within a solution

http://msdn.microsoft.com/en-us/library/ms180167.aspx

http://rlieving.blogspot.com/2009/06/how-to-deploy-ssis-package.html

http://blog.boxedbits.com/archives/25

http://decipherinfosys.wordpress.com/2008/09/16/deploying-ssis-packages-in-sql-server-2005/

http://bidshelper.codeplex.com/wikipage?title=Deploy%20SSIS%20Packages

---

Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Answer 15

U both deserve credit. Thanks Guys

Answer 16

One thing more, do we have an option to deploy particular package in the solution (if solution have , say five packages).

OR all the packages will get deployed.

Without the Deployment Manifest (package deployment technique that does allow you to deploy more than one package) you are constrained to deploying one package at a time.

PS: Of course, using the DTUtil in a bat file allows a certain degree of automation.

---

Arthur My Blog

Answer 17

If i am not worng, when we use deployment manifest file, it will deploy all the packages in the solution.

Am i right?

Answer 18

Yes, but I use this trick: right-click on the package and choose "Exclude From Project".

I of course add the package back right after the Manifest is built.

---

Arthur My Blog

Answer 19

whats the benefit of excluding from project

Answer 20

Oh I got you. thats exactly what i was looking for.

How we add the package back once the manifest is built.

Answer 21

Arthur, the second command is for file system. What if the ackage is on sql server rather than file system.

and

1. Once we deleted the old package from dev server and then we have to rune the second command to install the updated package there.

SO, WE DONT HAVE TO DO DEPLOYMENT AGAIN.Will the second command serve the purpose??

Answer 22

Oh I got you. thats exactly what i was looking for.

How we add the package back once the manifest is built.

To add the package back you click on the Packages folder, choose "Add Existing Item... " then pick the package that used to be part of the project and it will be brought back into the project.

---

Arthur My Blog

Answer 23

DTUtil is universal, it means it can take care of both: the packages in the file system or in MSDB. You only need to issue the proper command, to study the available commands bring up your command line (DOS window) and type in dtutil /? it will list all the available commands for it.

You are correct re #1.

#1 is the deployment process, yes, the 2nd command completes the process.

---

Arthur My Blog