Vendor Emails
4 posters
Page 1 of 1
Vendor Emails
Guys I have a vendor dimension with one row per vendor. It has email address which basically picks up the last one entered. Currently the business has requested all email addresses to be returned instead of one. What is the best way to handle this in the data model. I don't think flattening would be a good option because sometimes a vendor may have even 5 email addresses.
Thanks
Thanks
BIDW- Posts : 25
Join date : 2015-01-18
Re: Vendor Emails
Sounds like a good use of type 3 SCD. Flatten away!
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: Vendor Emails
Email adresses are descriptive attributes and the user just wants to read them.
I see the following options:
1. In your database you will have a table emails: as many rows as the vendor has.
If the user wants to see all these emails and the BI tool allows, you can creat a new page showing emails and the user can navigate to this information ( In Oracle BI for instance)
2. If there is no possibility, you can have an EMAILS attribute in Vendor dim table, where all the emails are stored. In this case you have just to show this column with the concatenated email addresses
3. Or you can combine the 2 solutions
4. Or create 2 columns for emails: MAIN (LAST)EMAIL, PREVIOUS EMAILS
I see the following options:
1. In your database you will have a table emails: as many rows as the vendor has.
If the user wants to see all these emails and the BI tool allows, you can creat a new page showing emails and the user can navigate to this information ( In Oracle BI for instance)
2. If there is no possibility, you can have an EMAILS attribute in Vendor dim table, where all the emails are stored. In this case you have just to show this column with the concatenated email addresses
3. Or you can combine the 2 solutions
4. Or create 2 columns for emails: MAIN (LAST)EMAIL, PREVIOUS EMAILS
gvarga- Posts : 43
Join date : 2010-12-15
Re: Vendor Emails
Just have an outrigger table with the vendor key and the email address. If there are significant other attributes for the email address you may consider a formal email dimension and a vendor/email bridge table. You may also consider a flag or timestamp to identify the most current address.
![-](https://2img.net/i/empty.gif)
» Vendor Dimension
» Customer Dim, Vendor Dim, or combined?
» Data Warehouse Vendor
» Modeling Price Bands for a Vendor
» Modeling of Vendor Quotes in Dimension Model
» Customer Dim, Vendor Dim, or combined?
» Data Warehouse Vendor
» Modeling Price Bands for a Vendor
» Modeling of Vendor Quotes in Dimension Model
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|