Enhanceents to LOOKUP | Microsoft Connect

Welcome, guest Sign in | Your Profile | Help

HOME

YOUR DASHBOARD

CONNECTION DIRECTORY

SQL Server Home Downloads Feedback Surveys

Enhanceents to LOOKUP by Jamie Thomson

Active

114

Type:	Suggestion
ID:	127229
Opened:	11/28/2005 10:56:36 PM
Access Restriction:	Public
Duplicates:	126084 126371 126378 126473 251562

Workaround(s)

view

A few problems with LOOKUP component:
1) Cannot set SQL statement that populates the LOOKUP cache dynamically. This means you cannot dynamically filter teh data in the cache - it would be a good idea to be able to do this. More info here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=147457&SiteID=1
2) There is no AlwaysUseDefaultCodePage roperty which there is if you use OLE DB Source. This is a problem if you're going against Oracle because a code page warning is automatically generated

These were discussed at length here:

Details (expand)

English

SQL Server 2005 - Enterprise Edition (32)

DTS

Windows Server 2003

US English

1) Put a property expression on SQLCommand property
2) Add a AlwaysUseDefautlCodePage property
Discussed at length here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=147457&SiteID=1

Improved Performance

Improved User Interface

Improved Performance

0 attachments

Posted by Microsoft on 1/13/2006 at 12:36 PM

Tracking as part of a parent bug

Posted by Jamie Thomson on 11/9/2006 at 11:37 AM

I want to re-iterate the importance of changing this. The inability to set the LOOKUP query dynamically is a major major shortcoming in SSIS. I'm coming up against this problem time and time again.

I'm surprised that a fix for this has not appeared in SP1 or in the first CTP of SP2.

Posted by Microsoft on 12/5/2007 at 1:10 PM

Jamie

I realize the importance of this issue and we will discuss in further detail later. Right now the issue has been moved to the next phase as it will not make the Katmai release.