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...
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.