I’m back from the MVP Summit and processing a staggering number of thoughts. Not only am I processing the brain dump of NDA technical goodness of exciting new stuff coming to the product, but a number of personal reflections. How lucky I am to have been somehow deemed worthy of this honor. How fortunate the SQL MVPs are in the number of sessions, pampering and genuine respect we receive from the SQL Server Product team. How lucky I am to be a part of one of the closest technical communities out there. The SQL Community calls itself family because we truly have a network of close, warm friendships. It dawned on me recently that I could go practically anywhere in the world (the world!) and find a colleague I have met from being a part of the SQL Community. I am a happy lady right now (in spite of the double ear infection).
Another benefit to you, my readers from my attendance to the Summit is a new motivation to continue sharing my knowledge with the community. That said, let me be the millionth prodigal blogger to apologize for my lack of blogging. Insert every lame but true excuse here: I’ve been busy, I’ve had things come up in my personal life, all true, but I know you want to hear from me.
Guess what guys? I’m speaking at PASS Summit this year! My session titled Data Quality Services—Finally! was selected and I get to go to the premier SQL Server conference and present on a topic which I find truly exciting. Data Quality Services (DQS) is new with SQL Server 2012. Along with Master Data Services (MDS), it represents Microsoft’s entry into Master Data Management (MDM).
The ideal use of MDS and DQS represent to me a paradigm shift in the way I.T. folks and business folks interact. These tools are not just another way for I.T. to develop solutions for “the business” based on requirements (whether those requirements are thoroughly documented via a watershed lifecycle or verbally shared with agile). DQS and MDS were explicitly designed for continued and iterative use by business users with expert Knowledge about their data. In MDM speak, these experts are called Data Stewards. I recommend that anyone in Data continue getting familiar with these concepts. Data Governance and Master Data Management are terms you are likely to see from now on. For more information I recommend David Loshin (http://mdmbook.com/) . His book, Master Data Management is a comprehensive guide to this topic. I’ve also found useful articles here , including articles on ways for I.T. to get “buy in “ from C-levels.
So, back to today’s post. As I was prepping my session for PASS Summit on Data Quality Services, I was extremely fortunate to be in communication with Matthew Roche and Matt Masson of Microsoft, who are also presenting on DQS (and MDS– actually all of EIM) at Summit. These two are both uber “ersum”, always willing to help me, answering emails at all hours of day and night.
Let’s dive in: Keeping data clean with DQS starts with creating a Knowledge Base. This is done in the Data Quality Client. Inside a Knowledge Base you create and maintain Domains. Single domains are the equivalent to a column or attribute in a database.
I check our blog every now and then and hang my head in shame. We don’t write, we don’t call. What happened? Well actually a lot of good things. We failed to announce on our site when Audrey became an MVP!