SSIS - Creating a Deployment Manifest

re: SSIS - Creating a Deployment Manifest

knight_devin@hotmail.com — Wed, 18 Nov 2009 18:44:28 GMT

That's strange I've never had that problem. Sounds like it you would be on the right track by editing the XML so i'm not sure why it would default back.

re: SSIS - Creating a Deployment Manifest

Rick Todd — Tue, 17 Nov 2009 19:20:46 GMT

Anyone know how to keep the CreateDeploymentUtility from reverting to False when I close and reopen the solution? I've tried adding the necessary XML to the dtproj and the dtprod.user files, but it always reverts...

Thanks,

Rick

re: SSIS - Creating a Deployment Manifest

knight_devin@hotmail.com — Fri, 06 Nov 2009 16:09:31 GMT

Sounds like you need to build the project again. I'm not sure why else it wouldn't update.

re: SSIS - Creating a Deployment Manifest

allen.lurey — Mon, 02 Nov 2009 20:50:17 GMT

Have run into a problem when using BIDS on my local desktop, and deploying DTSX, MANIFEST, DTSCONFIG file on the remote Database Server sql 2005. running the manifest, which initiates the deployment wizard is NOT updating the dtsx file with the server DTSCONFIG location. I am having to manually modify the dtsx file with the correct server location, and then importing the dstx file into msdb using IMPORT PACKAGE.

re: SSIS - Creating a Deployment Manifest

knight_devin@hotmail.com — Thu, 22 Oct 2009 17:55:19 GMT

Bruce

I haven't seen this problem before. At what point do you receieve the error? When you build the project to create the file or when you open it? Also if you can send me a screen shot.

re: SSIS - Creating a Deployment Manifest

brucek-1118507 — Thu, 22 Oct 2009 13:40:36 GMT

80040154 -error when trying to deploy manifest file.

what can I do about it?

Thank you.

Bruce

re: SSIS - Creating a Deployment Manifest

knight_devin@hotmail.com — Wed, 08 Jul 2009 20:57:51 GMT

Vasavi

Ahh I understand now, that makes sense. I can see that is a problem with the Deployment Manifest then.

re: SSIS - Creating a Deployment Manifest

vsankurathri — Wed, 08 Jul 2009 20:11:17 GMT

Knight,

The option we have is to specify the package path to save installation dependencies. Not the path to deploy ssis packages. When you select 'SQL Server deployment' as deployment option in Package Installation wizard, the ssis packages will be stored in msdb database in the folder specified in MsDtsSrvr.ini.xml. If you have subfolders under that, you can't deploy the packages using the manifest.

It is possible only through 'import package' option from SSMS.

Hope this is clear. Thanks for the feedback.

Vasavi

re: SSIS - Creating a Deployment Manifest

knight_devin@hotmail.com — Wed, 08 Jul 2009 19:03:07 GMT

Vasavi

When you run the Package Installation Wizard and select SQL Server deployment. You will have the option to specify the package path. So if you have a subfolder you can navigate to it there. The bad part about it is that you cannot see which packages are already in the folder you only see the folder name itself.

re: SSIS - Creating a Deployment Manifest

vsankurathri — Wed, 08 Jul 2009 18:47:10 GMT

Deployment of ssis packages through manifest would be nice, but we cannot browse the ssis sub-folders on the target server. If we use msdb to store packages, we will be able to deploy the packages only to the parent folder corresponding to the instance.

thanks,

Vasavi Sankurathri

SQL Server / Oracle DBA

The Hartford