If you are storing the packages in file system, then you just have to move the .dtsx file to the target location. Then you just need to run the package via dtexec.exe command, assuming yo have SSIS installed in the target machine. To take the execution of packages one step further, you can use SQL Server agent to run the package via job. btw, did you mean Business Intelligence Development Studtio when you say 'developer server'?Help Others! Don't forget to mark your thread as answered

this is good tutorial about how to deploy SSIS package and run it as sql server job: http://www.protalk.in/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/http://www.rad.pasfu.com

This could be really newbie question, i want to move my ssis 2208 package to another server. I have build ssis packages that runs well in developer server, and how to run it as task(really basic instructions please)? What file should i move and store to my live server? Thanks?

I store it in MSDB, are you sure just the dtsx file? it raises error. Thanks

I store it in MSDB, are you sure just the dtsx file? it raises error. Thanks yes just the .dtsx file. What is the error that you are getting? Is SSIS 2008 installed on the server you wish to move the package. If not you cannot do this. there is no backward compatibility. Tweet me..

Ok, remind me if i'm doing a mistake. I deploy my package and store it in MSDB. It works fine in development server. My question is should i redeploy the package, in my understanding i can deploy the package from Integration services deployment manifest file. I copied all the BIDS files to live server and also the database, the error is completely can not run. CMIIW. Thanks

what is error message exactly? http://www.rad.pasfu.com

To use Deployment Manifest, you should follow these steps: 1- Create the manifest first (set the properties in BIDS, and build your project then); 2- Copy all the contents of the Deployment folder in the project's folder into new server; 3- Run the .SSISDeploymentManifest file on the destination server. You will be able to deploy your package either to file system or SQL Server then.