Hi, I am using sql server 2008 . So far I have created SSIS packages on my local machine only. So I just want to know what are the steps to follow from creating a package locally to deploying them into production server?

There is not much difference in local and production package deployment. You can go for , File SystemSQL Server For file system approcah of deployment refer this : http://thebipalace.wordpress.com/2011/03/13/ssis-sql-server-and-file-system-deployment/ For SQL server approach od deployment refer this : http://thebipalace.wordpress.com/2011/03/13/ssis-sql-server-and-file-system-deployment/ In sQL server deployment in place of loacl server detail you need to ive production details. In file system double click the manifest file and deploy it to the loaction where you want to deploy. Regards, YB

Hi Yogish , Thanks for the reply but at the same time i have another doubt that when we will need the use of config file. So far as per my understanding we use to create then we generate the config file for the package and give it to testing team,if it's a success they forward it to the people handling production server or else if it's a failure they come to us. So how this config file and deployment fits in the same scenario.soumya swarup

There is one more type of package deployment that is XML configuration, Go through this, http://sqlscape.wordpress.com/2010/06/29/deploying-ssis-packages-with-xml-configurations/

Hi Yogish , Thanks for the reply but at the same time i have another doubt that when we will need the use of config file. So far as per my understanding we use to create then we generate the config file for the package and give it to testing team,if it's a success they forward it to the people handling production server or else if it's a failure they come to us. So how this config file and deployment fits in the same scenario. soumya swarup The easiest way to do a deployment is to install BIDSHelper: http://bidshelper.codeplex.com/ It's a free add-in for Visual Studio. You can right-click on a project or on a package and deploy it to any destination you want (SQL Server of filesystem). This is very easy for deploying packages that are stored locally to the development server. For automatic deployment from DEV to UAT or to PROD, I use dtutil: http://msdn.microsoft.com/en-us/library/ms162820.aspx You can incorporate this in .bat scripts to deploy more than one packages at a time. There are enough code examples on the web on how to do that. Configurations: a configuration (be it a file or a table in SQL Server), allows you to deploy the same package to different servers without changing the package itself. For example, you don't want your package in production to still update the database on the development server. In the configuration file, you add a configuration that sets the connectionstring of your destination database. In each configuration file, you change this connectionstring, so that your package always updates the correct database. So in short, you'll have 3 configuration files: one for the dev server, one for the UAT server (if you have one) and one for the production server. Beware: if the configuration fails for some reason, SSIS will take the values that were specified during design time in BIDS. So it's possible that your production package will still update your development server, if the configuration fails.MCTS, MCITP - Please mark posts as answered where appropriate.