Version Control for SQL 2012 SSIS Package

Joe_OJoe_O Posts: 2
edited July 28, 2014 5:52AM in SQL Source Control Previous Versions
We have started developing SSIS packages in SQL Server 2012 with packages being stored in the database. Can the packages be managed to store and deploy from source control using Red-Gate source control tools?
· Share on Twitter

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Thanks for your question. Red Gate SQL Source Control creates scripts for SQL objects, so it's almost completely scoped to objects that exist within a database, rather than server-level objects or externals like Integration Services packages.

    The strongest feature of SQL Source Control is the ability to express a database schema as a folder of DDL scripts - the management of these files afterwards is primarily done by integrating the source control system's existing APIs into SQL Source Control.

    Visual Studio and BIDS will already allow you to manage SSIS through a source control system using TFS or a third-party add-in like ANKH during the development process. If there is a story there where these tools don't fit into your processes, I am sure Red Gate would like to know if you have any special requirements where managing SSIS code in this way falls short.
    · Share on Twitter
Sign In or Register to comment.