Random articles from a puzzled DBA

SSIS

Subtitled – And I can’t edit them with VS 2010 either. Background I am currently testing our upgrade process, for moving all of our databases from SQL Server 2012 instances to SQL Server 2016. The SSIS projects that use the ZappySys PowerPack tools are failing with a particularly unhelpful message. In addition, attempts to open …

Background Recently I had to write an SSIS package that would import a series of csv files that had different numbers of columns within them. One file might have 15 columns, another 17 and another have something different again.

Background With the advent of the Integration Services Catalog, parameters for SSIS packages no longer need to be controlled using a configuration file (usually with the extension of ‘.dtsconfig’). Now the parameters can be stored within the Integration Services Catalog (and therefore, within the SSISDB database) and altered far more easily within an agent job.

The full message will also contain “The version number cannot be greater than the current version number”. Behaviour I have an SSIS package installed in an SSISDB which is on a server that run SQL Server 2012 (server A) and it needed to be copied to another 2012 instance (server B). My workstation has SQL …

In the previous article I covered the creation of the SSISDB – a new feature within SQL Server 2012 that is used to store all of the required information for an SSIS package. This article will cover the creation of a basic SSIS package that will require parameters to move data from a table on …

Although introduced in SQL 2012 I’ve never encountered this feature before, as all sites where I have previously worked have started with much earlier versions, and the old habits of implementing SSIS packages and jobs have just continued.

Background On a Dev server I have used Visual Studio 2010 to build and test an SSIS package. Having completed all of my testing I have now created an Agent task with the SQL Server instance on the same box, that should execute the dtsx package. However, when it attempts to execute it fails and …

SSIS can produce an inordinate number of error messages and numbers. Some of these can even be helpful and informative. Generally accompanied by an Error Code, one of the most popular appears to be “0x80070057” and can have a number of causes. Recently I came across this particularly helpful code when creating a Slowly Changing …