Two ways of improving your ETL with SQL 2012 #1

SQL 2012 has improved a lot when it comes to the possibility to create a better and more efficient ETL, and in this short intro, I would like to show you some of the things I find useful.

In this series of blogs I will show you:

  1. Projectdeployment instead of package deployment.
  2. Using Change Data Capture to improve performance.

Projectdeployment

One of the things that has always irritated me was the need to deploy a package instead of a complete project. To be practical, then I will show you how to deploy a project to a SQL Server 2012 instead of. It is very easy and gives you a lot of benefits. And it makes it easier to configure values that must change depending on the installation. On a scale from 1 to 10, where 1 is no new value and 10 is great new value, then I give this functionality 9.

Change data capture

This is also not new, and we have been able to setup change data capture since version 2008, but now even a newbie to ETL can setup changedatacapture and use it in Integration services. We have some new components that helps us. I would give this 10 out of 10.

This is simply brilliant, since it addresses one of the biggest problems in building a datawarehouse and getting a good performance: How do we only update and insert changed and new rows.

So let’s get started with projectdeployment.

Project deployment –>

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s