I need to determine whether to use the package deployment model or the new project deployment model.
Deployment of packages from development to QA will be done by developers and from QA to production by a designated person who is not a developer. Developers will not have access to the production box.
All of our ETL processes will be sending audit information to a central audit database. This information will include some performance data, but also information on the data: row counts (received, inserted, rejected), error data, and whatever else may be useful.
Other than ease of deployment, what are the benefits of using the SSISDB and the new project deployment model over package configurations?
Deployment of packages from development to QA will be done by developers and from QA to production by a designated person who is not a developer. Developers will not have access to the production box.
All of our ETL processes will be sending audit information to a central audit database. This information will include some performance data, but also information on the data: row counts (received, inserted, rejected), error data, and whatever else may be useful.
Other than ease of deployment, what are the benefits of using the SSISDB and the new project deployment model over package configurations?