Master Data Services, Microsoft SQL Server 2012 (Second Edition)

Master Data Services, Microsoft SQL Server 2012 (Second Edition)

Authors: 

Tyler Graham

Why I Recommend It: 

I will admit that I am a little weird in that I like reading about data quality and data management. In fact, this is what first attracted me to Microsoft’s Master Data Services (MDS) product. I cannot honestly say you need to read Mr. Graham’s book to figure out MDS. For the most part, I find MDS easy enough to grasp just by knocking around it. Even with its poorly organized, user interface, its reasonably self explanatory. Same for the Microsoft Excel plugin.

On the other hand, I found his discussion of the Staging Process gave me a jump start on maintaining data via ETL processes. I have even duplicated his tables of Import Type values and Column Names in my “cheat sheet” collection.

All the same, what I liked most about his book are his design and management tips. Among my favorite quotes.

“Master Data Services is not a data warehouse or a reporting tool. It is a data management tool.”
“MDS is best built from the top down, not the bottom up.”
“The computer scientist in us can override common sense.”
“Yet MDS is not designed as an automated system; it encourages and fosters user involvement.”

Enjoy the book! It is a great topic.

Quibbles: 

Chapter 5, Integrating Master Data Services With Other Systems, Relationship Table Fields.

OK, so while I cannot use a relationship staging table to maintain members of a collection, I can do so using the deprecated table “tblStgRelationship.” Problem I ran into, and have yet to find a solution to, is that I could find no way to trigger this batch in the staging process. Indeed, the deprecated table lacks a column for the Batch Tag. I suspect the solution is found in the documentation for the older SQL Server 2008 version of Master Data Services. Fortunately so far, my collections have not be so large that I cannot maintain them outside of the interface.