• Adam Thurgar

SSIS and source control

As I have written about previously, we are in the process of migrating a large amount of SSIS packages to AWS and also upgrading versions. One of the most difficult tasks so far has been to find the most current/latest package.

There are all these dtsx files of the same name in multiple directories Sometimes there are 5 or 6 different dtsx packages - but which is the right one? Some of these directories have names with version numbers in them e.g. _v4, others are named with environment indicators e.g. TST or STG, then others with the prefix or suffix of Old or Master etc etc.

This could have been so much easier if the SSIS packages were in some sort of source/version control. I am noy worried about the branching capabilities or multiple developers accessing the packages, this is purely for being organised. So I recommend pit your SSIS packages under source control.

4 views0 comments

Recent Posts

See All

Cardinality estimator

Recently I was asked by a software vendor to review a particular query that ran in under a second on a SQL Server 2014 installation at a compatibility level of 110 (SQL Server 2012), but when run unde

Index fragmentation

A law firm client, occasionally has issues with their legal software, that is provided by the global leader in this field. The response from the software provider is always the same - you have index f

Deleting large amounts of data

I had a client call me about wanting to delete a large amount of data from their database. They knew what tables they wanted to delete from. They also knew that deleting large amounts of data causes t