SQL Server 2014: SSISDB vs File System, deploying SSIS packages

  • Hello Everyone,

    One of my customer is upgrading their entire setup from SQL 2008 R2 to SQL 2014. They have around 14 SSIS packages, which they deploy using File System for SQL 2008 R2.

    I've suggested them to change the deployment process/method to SSISDB catalogue (Project deployment model) when we upgrade all SSIS packages to SQL Server 2014.

    They've asked me why should they change the deployment method? What are good reasons or advantages of SSISDB catalogue?

    I would like to convince them on this and would like to share the benefits of Project deployment model.

    Can anybody provide any convincing material or MSDN links, which could be shared with customer, so that they could understand the process and it's robustness.

    Also, is there any utility or tool like DTUtil for Project deployment model that could make the deployment super easy with SQL 2014?

    Any help would be much appreciated.

  • Refer to the link: https://www.mssqltips.com/sqlservertip/2450/ssis-project-deployment-model-in-sql-server-2012-part-1-of-2/

    MNDN doesn't really have pros and cons.

    I recently upgraded my company from SSIS SQL 2008 R2 to SQL Server 2014 and we went from package deployment to project deployment. Here are the Pros I think are BIG:

    - Automatic Logging: You don't need to worry about logging anything. A execution history is set for you.

    - Encryption: Everything is encrypted automatically including password. It's a big security risk storing passwords in plain text on SQL 2008

    - Versioning: By Default, upto 10 versions of your project are saved on the server, and you can rolllback to any version with a click. I have mine set to Last 20 versions. I did need to rollback one time after deployment, and it was so so so easy.

    - Reporting: You can setup Queries/Reports to query SSISDB for package executions and system health. I have a SSRS report that gets mailed to me every to looks at overall system health.

    CON: Manaing SSIDB. It can grow pretty quickly depending on how many times you execute package. We are a really heavy SSIS shop, and our SSIDB is upto 40GB now. We retain our history for 30 days.

    ------------
    🙂

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply