Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown Customers in DW due to NULL BuyingGroupID in WideWorldImporters.Sales.Customers #154

Closed
boscorat opened this issue Nov 14, 2016 · 2 comments
Assignees

Comments

@boscorat
Copy link

I've generated data in the WideWorldImporters database and run the SSIS package to populate the DW database. When I do this I get a large number of transactions with Unknown customers.
The reason appears to be that there are only two buying groups defined in the source database (Tailspin Toys and Wingtip Toys) and the rest of the customers have NULL for their BuyingGroupID. It looks as though this is acceptable, as not all customers would be part of a buying group, but the [Integration].[GetCustomerUpdates] procedure INNER JOIN's on to the BuyingGroups table. Due to this INNER JOIN, I'm only getting customer records in the DW database for Tailspin & Wingtip customers.
I've tried changing the INNER JOIN's in the [Integration].[GetCustomerUpdates] procedure, but this then breaks integrity constaints in the DW database so the customers won't load.
It may be that all customers should have a default BuyingGroup and something has gone wrong during my initial population of data, but I've checked through the scripts and it doesn't look like it.
Can anyone help?

@jodebrui
Copy link
Contributor

Thanks. This is a bug in the Integration procedure. We’ll get this fixed.

From: Jason Farrar [mailto:notifications@github.com]
Sent: Monday, November 14, 2016 3:16 AM
To: Microsoft/sql-server-samples sql-server-samples@noreply.github.com
Subject: [Microsoft/sql-server-samples] Unknown Customers in DW due to NULL BuyingGroupID in WideWorldImporters.Sales.Customers (#154)

I've generated data in the WideWorldImporters database and run the SSIS package to populate the DW database. When I do this I get a large number of transactions with Unknown customers.
The reason appears to be that there are only two buying groups defined in the source database (Tailspin Toys and Wingtip Toys) and the rest of the customers have NULL for their BuyingGroupID. It looks as though this is acceptable, as not all customers would be part of a buying group, but the [Integration].[GetCustomerUpdates] procedure INNER JOIN's on to the BuyingGroups table. Due to this INNER JOIN, I'm only getting customer records in the DW database for Tailspin & Wingtip customers.
I've tried changing the INNER JOIN's in the [Integration].[GetCustomerUpdates] procedure, but this then breaks integrity constaints in the DW database so the customers won't load.
It may be that all customers should have a default BuyingGroup and something has gone wrong during my initial population of data, but I've checked through the scripts and it doesn't look like it.
Can anyone help?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fsql-server-samples%2Fissues%2F154&data=02%7C01%7Cjodebrui%40microsoft.com%7Cca89eab1973b4293c5c908d40c7fac56%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636147189864947121&sdata=e8eLGJkPNL8iFJJwhhZ9iRKFqM1P8qUNMatJkz1fCyY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMuA9i71CpufZYuz5UbBOpMhJpUw38i0ks5q-EMIgaJpZM4KxNSp&data=02%7C01%7Cjodebrui%40microsoft.com%7Cca89eab1973b4293c5c908d40c7fac56%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636147189864947121&sdata=toDuimup4rFr%2BmDgvk76lg04mFmVNlsfpFXrsHwMpFQ%3D&reserved=0.

@jodebrui jodebrui self-assigned this Nov 18, 2016
@jodebrui jodebrui assigned jodebrui and unassigned jodebrui Dec 12, 2016
@jodebrui
Copy link
Contributor

Apologies for the delayed response. The issue was fixed, but I neglected to close the issue.
The fix is checked in, and will be included in the next release of the sample DB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants