September 1, 2009 at 2:28 pm
I am using SSISDeploymentManifest to deploy an SSIS packge to Productin box.
Here is what I did.
1. Copied pkg1.dtsx,pkg1.dtsConfig and pkg1.SSISDeploymentManifest to folder C:/SSISPackages
2. Douoble clicked on SSISDeploymentManifest
3. specified the server name
4. Selected windows authentincation
5. package path C:/SSISPackages
6. Click on next
I get the error 'path C:/SSISPackages does not exist on the server .. '
What am I missing here.
September 1, 2009 at 3:10 pm
Are you saying that you've copied all of this to your production server's C:\SSISPackages directory?
You don't need to copy the .dtsx, .config, and manifest anywhere. Use the deployment manifest from where BIDS creates it. The deployment manifest will handle moving all of your files for you.
Are you attempting a file system or SQL Server depoyment for your package?
September 1, 2009 at 3:16 pm
I have to say I truly detest the SSIS deployment utility..
I no longer use it. I build scripts using DTUtil to copy the DTSX files up into the Integration Services server.
I also create directories in the server like this
\Running Packages
\Stored Packages
\Stored Packages\File System
\Stored Packages\MSDB
\Stored Packages\MSDB\MyProject
\Stored Packages\MSDB\MyProject\SomeSubIfNecessary
This helps me stay away from what DTS looks like, just one big list with no clue what belongs to what. I don't ever drop anything into \Stored Packages\MSDB.
I have a different script for dev, qc, and prod, the only difference between them is the server name. You could even make that unnecessary if your rule was to ALWAYS run the script on the server the SSIS packages were being deployed to, but I didn't want to have that requirement so I hardcoded server names.
CEWII
September 1, 2009 at 3:28 pm
I copied all to the Production box and using Sql server deploy. It is SQL server 2008 and alos the BIDs is alos 2008.
September 1, 2009 at 3:29 pm
Can DtUtil be used to install the packages with config files. Please let me know the Syntax for that.
September 1, 2009 at 3:31 pm
Try deploying it to your SQL Server without copying the files first.
Alternatively, you can connect to your production SSIS instance and import the package there.
September 1, 2009 at 3:34 pm
Config files are just files that are referenced. I guess I don't understand your question.. You can copy the files to wherever you want them to go, preferable where the package is expecting them..
CEWII
September 1, 2009 at 5:01 pm
I am using SQL server 2008 Bids.
1. Please tell me how to deploy an SSIS package with dtsconfig file on prod SQL server.
a) as per suggestion I tried from my machine with manifest file, but still the package path not found error is coming. Even when I try to browse the packge by clicking the browse button it doesn't give option to select from C drive.
I have both 2005 and 2008 on my local machine is this causing the problem?
2. If I need to use DTUtil. I beleive the following is the syntax.
dtutil /DestS [servername] /FILE [filename].dtsx /COPY SQL;[foldername]\[filename] /QUIET
in this case where is the config file being specified in the syntax.
September 1, 2009 at 10:46 pm
I admit I've never specified the config file from here I always setup the package to go for it.. Hmm.. Let me look..
CEWII
September 2, 2009 at 8:25 am
September 2, 2009 at 12:58 pm
I got it resolved.
Here are the steps.
1. Created the packge1.SSISDeploymentManifest
2. Copied the files from local box to production box folder. C:/SSIS_Deploy/
a.packge1.dtsx
b.packge1.dtsconfig
c.packge1.SSISDeploymentManifest
3. Double clicked on the SSISDeploymentManifest and selected SQLServer deploymnet
4. In the next page of the wizard selected the server name
5. In the path clicked the browse button (...) and selected the folder SSISPACGES. that keeps the path as / . this is where I have all the confusion earlier. I was trying to select the local C:/SSIS_Deploy/ folder and keep getting the path not found error.
6. Click next, this gives the installation folder path. Select what ever folder path you want from the browse button.
7.Now it gives the option to select the config file. Selected the config file from packge1.dtsconfig.
8.click next and finish.
With the above steps the packge1.dtsx and packge1.dtsconfig files are copied to the folder specified in step6.
Now the package is successfully deployed to sQL server, but to run this package as SQL scheduled job.
Create a job and select the SSIS package and also add the config file in the job set up. There is a separate tab to add the config file.
the same thing of deploying to SQL server can be done from DTUtil. DTutil only copies the .dtsx but you can use the regular copy command in your bat file to copy the .dtsconfig to the folder.
then setting up SQL agent job is same as explained above.
September 2, 2009 at 1:01 pm
1. Created the packge1.SSISDeploymentManifest
2. Copied the files from local box to production box folder. C:/SSIS_Deploy/
a.packge1.dtsx
b.packge1.dtsconfig
c.packge1.SSISDeploymentManifest
3. Double clicked on the SSISDeploymentManifest and selected SQLServer deploymnet
4. In the next page of the wizard selected the server name
5. In the path clicked the browse button (...) and selected the folder SSISPACGES. that keeps the path as / . this is where I have all the confusion earlier. I was trying to select the local C:/SSIS_Deploy/ folder and keep getting the path not found error.
6. Click next, this gives the installation folder path. Select what ever folder path you want from the browse button.
7.Now it gives the option to select the config file. Selected the config file from packge1.dtsconfig.
8.click next and finish.
With the above steps the packge1.dtsx and packge1.dtsconfig files are copied to the folder specified in step6.
Now the package is successfully deployed to sQL server, but to run this package as SQL scheduled job.
Create a job and select the SSIS package and also add the config file in the job set up. There is a separate tab to add the config file.
the same thing of deploying to SQL server can be done from DTUtil. DTutil only copies the .dtsx but you can use the regular copy command in your bat file to copy the .dtsconfig to the folder.
then setting up SQL agent job is same as explained above.
September 3, 2009 at 12:04 am
I have a different script for dev, qc, and prod, the only difference between them is the server name. You could even make that unnecessary if your rule was to ALWAYS run the script on the server the SSIS packages were being deployed to, but I didn't want to have that requirement so I hardcoded server names.
September 3, 2009 at 12:08 am
With the above steps the packge1.dtsx and packge1.dtsconfig files are copied to the folder specified in step6.
Now the package is successfully deployed to sQL server, but to run this package as SQL scheduled job.
Create a job and select the SSIS package and also add the config file in the job set up. There is a separate tab to add the config file.
the same thing of deploying to SQL server can be done from DTUtil. DTutil only copies the .dtsx but you can use the regular copy command in your bat file to copy the .dtsconfig to the folder.
September 4, 2009 at 7:41 am
This was removed by the editor as SPAM
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply