Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Register Now and get your question answered!
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 Best Practice for SSIS
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

4 Posts

Posted - 01/18/2013 :  14:58:06  Show Profile  Reply with Quote
Hi Folks,

We used to only have 1 production SQL 2008 R2 server - so all SSIS packages were developed ON that server....probably not best practice.

I was able to convince my Director that we needed a development, or staging server for SQL - I got it!

So now I am developing SSIS packages on the SQL development server - cool! But now I'm wondering what the next step is...

I think I have two choices:

1) Use the development server to run the SSIS packages on - including for production databases on the production server - probably not best practice

2) Deploy the packages to the production server and run them from there - probably best practice...?

And then that begs my next question - a package developed on "DEV" and deployed to "PROD" won't work anymore, since the package was developed on a different server, all the pointers, etc would be different...? So what's the best practice for deploying an SSIS package from a DEV server to PROD after it's working on DEV?

I've never deployed a package to a different server before because they were always created on production. I've heard of "dynamic" packages, but don't really know what that means...

Any help appreciated.

Very Important crosS Applying yaK Herder

52326 Posts

Posted - 01/19/2013 :  02:36:49  Show Profile  Reply with Quote
you should be developing and test running the packages in DEV server and then once happy you should deploy them to PROD server.
The properties of connections, variables etc can be made dynamic using package connections.


SQL Server MVP

Go to Top of Page

James K
Flowing Fount of Yak Knowledge

3873 Posts

Posted - 01/19/2013 :  06:15:12  Show Profile  Reply with Quote
This article by Robert Sheldon is another good read. I have found that Robert Sheldon's articles are usually very lucid and clear.

You may find this tutorial useful - discusses deployment options

Edited by - James K on 01/19/2013 06:16:32
Go to Top of Page

Starting Member

4 Posts

Posted - 01/21/2013 :  07:20:06  Show Profile  Reply with Quote
Really good info guys - thank you!
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000