August 12, 2013 at 1:15 pm
we are moving to sql 2012 and considering moving to the project deployment model due to environments.
Aside from the environments feature we lose the ability to deploy single packages.
Can you guys educate me why single package deployment is a bad idea, and why the project deployment model is "better". i know its all relative, but id like to hear other peoples thoughts.
August 12, 2013 at 1:29 pm
Project deployment model:
* there is a real concept of "project" --> might force you to do more source control
* project connection managers
* parameters & environments (I find those eventuelly more manageable than configurations)
* parameter driven child packages with the new execute package tasks (as it should be)
* built-in logging & reports (although this can cause a bit of overhead)
Package deployment model:
* you don't need to do any upgrade
* you can deploy single packages
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply