THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is

SSIS is Case-Sensitive

This blog has moved! You can find this content at the following new location:

Published Friday, May 28, 2010 8:00 AM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



jorg said:

Hi Andy,

I've blogged about this a while ago and another way to "fix" this is to set the CacheType property of the Lookup to partial or none. This way not SSIS but SQL Server does the lookup comparison. You find my blog post here:

By the way: I think also using UPPER like you describe is the best approach.

May 28, 2010 8:02 AM

unclebiguns said:

Excellent post!  I like the idea of a join field.  I have not done that, but will likely make the change as I work with SSIS in the


May 28, 2010 9:39 AM

ssis newbie said:


I have done the lookup transformation by using upper() function. but by doing so, i lost the original case of the value.

With your idea, the original case can be retained. thanks for sharing the idea.

September 7, 2011 11:51 PM

John Andrews said:

Hello Andy.  SQL Server case insensitivity has me spoiled, and, consequently, made the rookie mistake of not respecting the case sensitive nature of SSIS.  Thanks for the reminder.  -john-  

May 28, 2015 7:11 PM

Dennis said:

The comparison flags in the advanced editor of the oledb source also do the trick.

May 25, 2016 9:24 AM

Leave a Comment


This Blog



My Latest Book:

Community Awards

Friend of Red Gate

Contact Me


Privacy Statement