Database Design Models / Considerations Using Basic Data Services

Question

I'm trying to find a good source of information about database considerations / templates and / or tables that you need to know about when designing a data warehouse and using MDS / DQS components ... things like adding the "current flag", "creation date", " end date "," last updated date "for slowly changing dimension tables ... but specific to MDS.

There was a comment or two on several MDS articles / blogs stating that "once your MDS model is made, periodic updates should be planned to apply any changes to the master data made in MDS to your DW production tables."

For example, as a developer, are there any additional columns that I would like to include in my dimension tables, such as a flag indicating that the data in this record was updated using the MDS update process? Or perhaps a separate database schema for tracking changes associated with MDS, with FK constraints in production tables?

Also, I don’t have enough rep to create a new tag, but it would be useful to have the [Master-Data-Services] or [MDS] tab

Answer 1

in one of my projects, we used MDS as the central repository for enities, which required the attention of stenographers. Each data warehouse updates ETL pumps, which also extract data from source systems and MDS. Historical MDS data was stored in a data warehouse using a slowly changing measurement process.

In MDS subscription mode, there is a timestamp for the last time a record was changed so that you can easily recognize the changed items.

Hope this helps.