settingsLogin | Registersettings
Show Menu

MDS in DV architecture

+2 votes
Hey there, folks,

I have decided to add a MDS using SQL Server Master Data Services 2012 to an architecture I am working on. I have run into considerable confusion because I am not sure how to put the ETL process. I have two ideas, which I've listed below.

Number one: Between Staging Area and DV. Doing it this way, data from DV will be extracted by the ETL process and will be loaded into the MDS. Afterwards, data from MDS will be extracted and loaded into DV.

Number two: Between DV and Dimensional Data Store. The ETL will extract all relevant data from DV and load it to MDS before extracting it from MDS and loading it into DDS.

Which option do you think is the best?
asked Dec 1, 2013 in Architecture by J_King (240 points)

3 Answers

+1 vote
Best answer
In general, Master Data, the managing of data in an organization, originates downstream from the data warehouse or Data VaultData Vault is a means of integrating data from source systems via its business keys. After the data has been christened master data by the business, you should make it an up-stream source system for the staging areas. When you properly implement data solutions, all source systems will align, in real-time, to the reference data. They'll become a system of record and be reference data themselves.
answered Jan 6, 2014 by Les_Inspecteur (580 points)
0 votes
The question is, how do you plan to use MDS? MDS is a means of organizing data. I don't have any prior experience with MDS, but from what I can tell, it is something that you want to use as a source to the DV, not as a direct feed to the data marts.
answered Dec 19, 2013 by C.Black (580 points)
I thought you should directly feed data marts because of the schema of a MDS. It's quite different from DV.
+1 vote
I have used MDM solutions with the DV architecture in the past. From what I can tell, it sounds as if you are viewing the Customer MDM domain and not the product. In my opinion, the MDM model is the right thing to use as your MDM hub. However, you will need to consider the overall purpose of the MDM and determine that for yourself.

Here's another suggestion that fits right between your option one and option two. You add another stage after the DV but before the Business DV layer. The DV will feed the MDM when you also need Governance Data Stewards involved with merge and purge actions. This way, the MDM will be in charge of the customer number. As a result, you will need to feed the MDM to the DV as well as any and all applications.

As the MDM will be creating and managing the persistent customer number, DV will not need to do that job.
answered Jan 24, 2014 by E.Barber (320 points)
reshown Mar 16, 2015 by molschimke
Scalefree Scalefree

Upcoming Trainings

  • July 01 to 03 - Amsterdam (English) Data Vault 2.0 Boot Camp and Certification

  • August 05 to 07 - Berlin (German) Data Vault 2.0 Boot Camp and Certification

  • September 9 to 13 - Hanover WWDVC EU

  • September 16 to 18 - Brussels (English) Data Vault 2.0 Boot Camp and Certification

  • October 21 to 23 - Hanover (German) Data Vault 2.0 Boot Camp and Certification

  • November 18 to 20 - Amsterdam (English) Data Vault 2.0 Boot Camp and Certification

  • December 02 to 04 - Dusseldorf (German) Data Vault 2.0 Boot Camp and Certification

  • December 16 to 18 - Zurich (English) Data Vault 2.0 Boot Camp and Certification

  • Contact us for inhouse training engagements.
    Visual Data Vault: Logical Modelling for Data Vault - Free Download!
    Scalefree is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.
    Permissions beyond the scope of this license are available in our license. | DWH Wiki | Recent questions RSS feed | Imprint | Provided by Michael Olschimke