November 18, 2007 at 3:37 pm
Hi,
I hope someone could guide me on this.I have tried many many attempts for the past few days and am not sure if I am going in the right way.I have to deploy a SSIS package that I have created in my developement server into my production server. Production server has same database name as development server.
Steps that I have taken are:-
1) Save my SSIS pacakge in SQL server [development box]
2) Cretead a package configuration as an XML
What is my next step to bring it to the production server,schedule as a job without losing the password.
What do I need to edit in the XML file ?
I am really not sure of what I am to do on the production server .Please Help me out on this !
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 5:30 am
Is protection level of your package set to EncryptAllWithPassword?
Is package supplied with PackagePassword?
Is package deployed and you have all files (.dtsx, .SSISDeploymentManifest and others) i deployment directory?
November 19, 2007 at 7:51 am
Is protection level of your package set to EncryptAllWithPassword? YES
Is package supplied with PackagePassword? YES
Is package deployed and you have all files (.dtsx, .SSISDeploymentManifest and others) i deployment directory?
I hope you could guide me one the approach I would need to implement my package onto production server .
What do I do next,after package is tested in development server, saved package in MSDB db [Development Server], created an XML config file on development server ?
I have no clue on what I need to do on Production Server.
Do guide me through.Thank You !
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 8:12 am
jasmeet_lett (11/19/2007)
--------------------------------------------------------------------------------
Do guide me through.Thank You !
1. In Solution Explorer click on package (top most element) and chose Properties option.
2. Click on Deployment utility
3. Change CretaeDeploymentUtility to true, register in mind DeploymentOutputPath
4. Click OK.
5. In solution Explorer right click on package and run Build option.
6. Go to path given by DeploymentOutputPath and what you see?
[to be continued... :)]
November 19, 2007 at 8:18 am
This link should help you. http://msdn2.microsoft.com/en-us/library/ms365301.aspx
November 19, 2007 at 9:37 am
7. Copy all files from deployment path to production server.
8. Double click on file with .SSISDeploymentManifest extension an deploy package od production server
9. Choose SQL Server deployment option
10. Select server and authentication type
11. Enter password
12. After deploying package od production server go to SSMS SQL Server Agent->Jobs option, right click New Job
13. IN General option type name of the job
14. move to steps option and click New...
15. type step name and select SQL Server integration services package from Type list
16. select SQL server as source, select production server and select authentication and select package clicking on ... button
17. move to schedules option and an click on New... button and create schedule type as you want.
18. click ok button.
Package is now ready to action.
November 19, 2007 at 9:57 am
Marek, This is great. I never knew this can lead in a package migration wizard. Well, my problem is, the other server is not at all connected to my developer server. So, in the wizard, it will not show the other prod server. How do I deal with this. Yes, I have password for everything, but there is only one and it is the same across the network. I had to use encrpt all with password as this is the company policy.
Another issue I was facing is whenever I create a package configuration(previously) the password will get dropped and I have to reconnect ALL the connection manager for it to work again. I am talking about even in my own developer box. This was irritating!!! Arrgghh!!! Are you sure that if I build the package like you said, I will not face the same problem again. Please lead me thru. I appreciate your help and envy your knowledge. Thanks
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 10:16 am
Do you have VPN connection to your production server?
November 19, 2007 at 12:49 pm
No. we use citrix to get in there. Thats totally a different network.
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 12:58 pm
OK, but you can copy files between your station and production server? Is it possible to remote run programs on the production server?
November 19, 2007 at 1:03 pm
Yes, i can. But how do i put it together in the package wizerd though?
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 1:15 pm
Copy all files from {your project directory}\bin\deployment directory to any directory on the production server.
From this directory on production server run file named as your package but with .SSISDeploymentManifest extension (by double click on this file) and apply all steps as it was shown by me earlier.
November 20, 2007 at 7:52 am
Thanks for your reply. It really works well now. Thanks again:D
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
June 5, 2008 at 5:00 pm
I have the same thing now....I ve to deploy packages to the production server....its really nice that you mentioned all the steps in an order....but once we move the packages to the production server we ve to edit the XML configuration file and change the connection properties....can you explain me how to do this(I mean do we ve to change the server name in all the places we found in XML file)?? and do we need to create environmental variables to store the path?? I just created XML file...I did nt set up environmental variables...
Hi Mr.Lookup_BI, I just posted here as we both have the same issue...I dunno if I shud not post this here..:(
June 6, 2008 at 1:41 am
hey Maddy,
One environment variable will do which will explain where the configurations reside (in the xml file or on the SQL server)
My preference is SQL server, because anything that is encrypted shows to whomever does the package deployment if you choose the xml option.
~PD
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply