Hi, just a question about 'retraining" ourselves in the SQL 2012 Project deployment model. We have a number of developers, who would in the past develop their 'packages' and when ready for deployment would send a single dtsx file to the DBA team. That team would deploy it to the MSDB repository on a qual environment typically, schedule SQL agent jobs as needed etc.
So question #1 is what steps can the developers take in the SQL 2012 model to provide the DBA's the easiest deployment method. If the developer provides just a .dtsx file, then the DBA's have to run through the "Integration Services Project Conversion Wizard" to generate an .ispac file correct? Then you use the (automatically linked) "Integration Services Deployment Wizard" to deploy to where the project will be located in the Integration Services catalog?
We understand that the developers can be given permissions to create a project folder and deploy the project themselves right out of Visual Studio, but we don't want to grant the user membership to the ssis_admin role and our security model is not to allow them to deploy directly to the server especially in Prod.
What are we missing?
Thanks
Matt