Lookup Component causes package to be updated each time the data flow is viewed in BIDS

Welcome, guest Sign in | Your Profile | Help

HOME

YOUR DASHBOARD

CONNECTION DIRECTORY

SQL Server Home Downloads Feedback Surveys

Lookup Component causes package to be updated each time the data flow is viewed in BIDS by john_welch

Active

Type:	Bug
ID:	482369
Opened:	8/11/2009 12:40:34 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Viewing a data flow with a Lookup component in it causes the package to be modified. This is most visible when you are using source control, but you can also see the behavior if you simply mark the package as read-only in the file system. Opening the data flow evidently causes some of the metadata related to the Lookup's output to be refreshed, and the package is flagged as dirty in VS.

This is a problem when using a source control system, particularly if it is not configured for automatic checkout. The user is prompted to check out the package when the data flow is viewed. If they elect not to check out, they are prompted multiple times (evidently once for each connected output from each lookup in the data flow). After canceling out of all the check out prompts, you get the following message:

TITLE: Microsoft Visual Studio
------------------------------

The connectors could not be refreshed for the following paths:
    Path 'Lookup Match Output' (ID: 240): The checkout was canceled by the user.
    Path 'Lookup Match Output' (ID: 310): The checkout was canceled by the user.
    Path 'Lookup Match Output' (ID: 332): The checkout was canceled by the user.

------------------------------
BUTTONS:

OK
------------------------------

Details (expand)

English

SQL Server 2008 SP1

Integration Services (DTS)

Windows Vista 64-bit

US English

Create a package. Add a data flow, an OLE DB Source pointing to AdventureWorks2008, a Lookup, and a Union All. Configure the source to retrieve some data, configure the lookup to use the same OLE DB connection manager, and to retrieve an appropriate set of data to match with the input. Connect the Lookup's Match output to the Union All.
Save the package, and close it. Open the package, and select the data flow tab, without changing anything.

The package will be flagged as dirty in VS, even though nothing has been modified.

There are no modifications to the package.

X64

1 attachments

Lookup.zip

Posted by Rafael Salas on 8/11/2009 at 7:41 PM

I am also suffering from this issue. But here are some of my observations:
After further inspection, it seems like the culprit are the connection managers and their package configurations. When you open the data flow the connection managers are validated and package configurations are loaded, in my case the connection string loaded from my local configurations differ from the ones in the package before I opened it (kind of expected if, for instance, last person saving the package had different connection strings).

Here is another variant of the issue. If you open a package and try to open the package configuration organizer you will get the same prompt to check out the file from source control.

This behavior is very annoying specially when all you want is to ‘look around’ packages.

Posted by Microsoft on 8/27/2009 at 9:39 AM

Thank you for your submission. We will be reviewing your information and providing you feedback on our findings and progress. Thanks for your interest and support of SSIS.