Updating ssis packages

I described some ideas I had for SSIS branching strategies when you’re using source control a while back.

I’d like to add the following high level recommendations to that post: Now, there are probably cases where single package updates for an SSIS project deployment can come in handy (even when you’re using source control, producing regular builds off the integration branches, etc). If you have one of these scenarios, I’d really like to hear it – either via Connect, or by posting here (or ideally, both).

We have a scheduled job that executes this package, and also overrides the SMTP connection string so that the package can target the test or production mail server, which makes it possible to keep a single service on both our test and production servers, just configured differently.

We recently changed the server name of our production mail server and went into the scheduled job and changed the command prompt values that run to point to the new server.

The central one being source control management of your SSIS packages. ) When I ask for details about the scenarios that people require single package updates for, it typically turns out that they are doing one or more of these “should not” things in their environments.

Let’s compare developing an SSIS solution to developing a C#/. If all of these things are red flags for application developers, then why do people do them with SSIS solutions?

Often these situations are easy to resolve if you know how to proceed.

updating ssis packages-7

Script tasks are a great way of extending SSIS functionality, when the buit-in functionality isn't quite Script tasks are a great way of extending SSIS functionality, when none of the buit-in components are quite right for the task you need to perform. No worries, once again Robert Sheldon is on hand to provide easy instructions on how to do it.

I created a SSIS package for a CRM project I was working on recently.

After deploying and executing the SSIS package in the client’s production environment, it completed successfully, but zero records were created in the target CRM entity. We realised the BDD had not been installed on the production server after hours of problem solving.

It’s actually a feature we considered, and one that I (initially) argued for, as I know it is a common practice with SSIS solutions built for SQL Server 20.

However, I was quickly convinced that the scenarios that require of a project can be solved using team development best practices and procedures.