"Microsoft SQL Server 2005 Integration Services (SSIS) provides tools that make it easy to deploy packages to another computer." Really now, because it looks like about 500+ steps to me. I have a job to get done, I need to get something done. I know, I know. I'm whining. Facebook: Zamdrist Roleplaying: Elliquiy

what is your question? do you want to use Deployment Utility of SSIS? if yes, in the BIDS, right click on your project in project explorer, then select properties, in the properties window, then select Deployment Utility tab, and then set CreateDeploymentUtility to true. then a folder in this default address: <your project physical address on Hard drive>\bin\deployment will create with all packages in the project, all miscellaneous files , and project deployment manifest file. you can copy whole deployment directory to the computer which you want to install packages there and then just run the *.SSISDeploymentManifet file to run the installer wizard. http://www.rad.pasfu.com

I won't lie - deployments from anything but the IDE are painful in the MSBI stack its my one big complaint. We wrote powershell scripts that check code out of source control and then deploys it for SSRS Native, SSAS, SSIS, and BizTalk (and sometimes its still not pretty). I think there are some Codeplex projects out there aimed at making deployments easier.

Natively deployment methods kind of suck. If you want to try a 3rd party solution (disclosure: I work for Pragmatic Works) check out BIxPress (http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/Default.aspx). Makes SSIS development a hell of a lot easier, that includes deployment and monitoring/auditing.Jorge Segarra SQLChicken.com || Follow me on Twitter! || SQL University Please click the Mark as Answer button if a post solves your problem!

what is your question? do you want to use Deployment Utility of SSIS? if yes, in the BIDS, right click on your project in project explorer, then select properties, in the properties window, then select Deployment Utility tab, and then set CreateDeploymentUtility to true. then a folder in this default address: <your project physical address on Hard drive>\bin\deployment will create with all packages in the project, all miscellaneous files , and project deployment manifest file. you can copy whole deployment directory to the computer which you want to install packages there and then just run the *.SSISDeploymentManifet file to run the installer wizard. http://www.rad.pasfu.com Reza. Thank you. I followed these steps to a "T", deploying the package to the SQL server I would wish to schedule it to run on. I didn't get any error messages, and I chose the default installation path. I guess in my ignorance I presumed I would see my package somewhere on the server via SSMS, say under "Management" or "Server Objects", but I've looked everywhere and don't see it. Am I just missing the whole point of this? ThanksFacebook: Zamdrist Roleplaying: Elliquiy

Wait...I'm starting to put it together. Connecting SSMS to Integration Services via Object Explorer...Facebook: Zamdrist Roleplaying: Elliquiy

I found the instructions here. http://msdn.microsoft.com/en-us/library/ms365338.aspx Just seemed a bit overwhemling at first. Reza's brief explanation is essentially what these instructions detail.Facebook: Zamdrist Roleplaying: Elliquiy