Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Devin Knight

Devin is a BI consultant at Pragmatic Works Consulting. Previously, he has tech edited the book Professional Microsoft SQL Server 2008 Integration Services and was an author in the book Knight's 24-Hour Trainer: Microsoft SQL Server 2008 Integration Services. Devin has spoken at past conferences like PASS and at several SQL Saturday events. He is a contributing member to the Business Intelligence Special Interest Group (SIG) for PASS as a leader in the SSIS Focus Group. Making his home in Jacksonville, FL, Devin is a participating member of the local users’ group (JSSUG).

SSIS Denali Resolve References

One of the new features in SSIS Denali that I’m really excited about (Other than the ability to Undo ctrl-z) is the new resolve reference functionality that was brought into the product from the Parallel Data Warehousing team.  Resolve references is solving the problem that occurred when you created a package with a data flow and you made just about any change above your destination.  You would see red x’s on your transforms and to fix the problem you had to try and figure out what the below image was telling you:

If this has ever given you headaches before you will be please to find out with the release of the SQL Server Denali CTP that the resolve references tool will help.  To walk you through this first I’ll demonstrate the problem in the current version of SSIS and then show you how Denali’s resolve references eases the pain.

I have 3 sources as you can see above.  Each source is essentially the same:

·         Source 1 was used to originally configure the data flow. 

·         Source 2 is an exact duplicate of Source 1. 

·         Source 3 is the same but has one of the column names changed.

When you change from one source to another you get the dreaded red x and upon opening the Derived Column the Restore Invalid Column Reference Editor opens as usual.  The same would occur if I connect Source 3.

Resolve reference in Denali makes this easier.  Here’s the same example in Denali:

When I change from Source 1 to Source 2 in SSIS now in Denali it allows this without any problem because the sources are actually exactly the same (as you would hope it would react).

 

When I change to Source 3 I still have the red x problem I had in previous version of SSIS but instead of it being on the transform itself it is now on the data flow path.  This means you can actually fix the reference simply by right click on the path and select Resolve References as shown below.

Upon select the Resolve Reference button it opens a new dialog box that can be used for remapping your columns that have are currently invalid.  Like I mentioned this editor is very similar to the Parallel Data Warehouse adapters for SSIS.  The interface is very nice too.  It’s completely drag and drop to reapply your references as shown below.  When you finish your mapping you click OK and you can result development as normal!

Some other nice features here are:

·         Automap columns based on matching names

·         Filter under each section to find your columns quicker

·         Copy and paste the columns you have selected to be mapped to the clipboard

·         Delete unmapped input columns

·         Preview Changes before you confirm them

Hope this new features gets you as excited as I am about it.  I will try to continue to post new SSIS Denali features as I learn them myself.

Comments

Posted by Mark Stacey on 21 November 2010

Yeah, I logged this as a connect issue like a million years ago, saw it marked as fixed just the other day -  lots and lots of happiness :)

Leave a Comment

Please register or log in to leave a comment.