July 23, 2009 at 6:51 am
SSIS Deployment 101 question.. the only way I know how to deploy SSIS pkg's is to:
- right mouse click the VS Project
- select properties, deployment utility
- set 'Create Deployment Utility' to true
- BUILD the project (which builds ALL the packages & gen's manifest)
- then Click the manifest file and deploy to target SQL Server
If I make a change to 1 SSIS pkg and want to build/deploy only that Pkg, how would I do so?
thx in advance
July 23, 2009 at 11:42 am
I personally don't like to use the method you describe as its very easy to overwrite an existing package because it does not give a warning.
If you log onto integration services, you select 'stored packages' and right click on MSDB to select 'import package. It will bring up a box where you select the package location. In this case, it's probably on your computer, so pick 'file system'. Under package path browse to the location of your dtsx file. Finally, select the appropriate package level and hit ok. If there happens to be a DTSX package with the same name you'll get a warning.
There's also a third way of deploying a package by dragging and dropping the file to the packages folder where SQL Server was installed. In my case, it's Program Files\Microsoft SQL Server\90\DTS\Packages. If you use this option, you need to make sure that the folder is part of your backup schedule.
July 23, 2009 at 3:11 pm
I've been fortunate to only have to use the, "File --> Save Copy of [package name] As..."...then select, "SQL Server" or "SSIS Package Store" as the Package Location.
July 24, 2009 at 12:14 pm
Uncle Moki (7/23/2009)
I've been fortunate to only have to use the, "File --> Save Copy of [package name] As..."...then select, "SQL Server" or "SSIS Package Store" as the Package Location.
I had no idea you could data that. This brings up the same window as importing it but without the extra step;)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply