In this blog-post, we would see what does it mean to lock a knowledge base in Data Quality Services? So the lock on the Knowledge Base indicates that there are unsaved changes in the Knowledge base when you or someone else was working on it.
In the Data Quality Client, Here’s how a lock on the Knowledge Base looks:
And here are few points for a locked knowledge base:
1) If you did not lock the Knowledge Base then you can open it in read-only only
2) if you locked the Knowledge base, you can open and edit it. The Knowledge base would be opened in the state that it was closed in.
3) A user working on the Knowledge base can unlock it by publishing it or by unlocking the knowledge base.
4) By positioning the cursor on the knowledge base – you can see who locked it:
In this blog post, we saw what does a lock on a knowledge base in Data Quality Services mean?
A quick post on step – by – step to delete a Knowledge Base (KB) in SQL Server 2012 Data Quality Services (DQS):
1. Open the Data Quality Client
2. Click on “Open Knowledge Base”
3. Select the KB > Right Mouse Click > Delete.
Note that it also allows you to Rename, Open and see properties of a Knowledge Base via this Knowledge Base Management UI.
That’s about it for this post. I took me five minutes to figure how to delete a KB and so I thought I would document it if someone is not able to find this option as quick as they might have thought. Happy Data Cleaning!
This Blog Post is meant to share how I think of what is KnowledgeBase in SQL Server 2012 Data Quality Services (DQS) – In my mind, Knowledge Base (KB) captures:
1. WHAT needs cleaning
2. HOW to clean what needs cleaning.
Let’s dive a little deeper, In DQS – a Knowledge Base let’s you do three things: Knowledge Discovery, Domain Management & Matching Policy.
1. Knowledge Discovery:
This activity helps you find “WHAT” needs cleaning. DQS has inbuilt algorithms that helps in analyzing errors, inconsistencies and data quality issues in the sample data-set.
2. Domain management:
This activity helps in defining the rules that will be applied to create “HOW” to clean the data.
3. Matching Policy:
This activity helps in identifying “WHAT” needs to be De-Duplicated (De-Dup) and then it goes about helping create the “HOW” to De-DUP the data.
In this short blog post, I shared how I think of what is Knowledge Base in SQL Server 2012 Data Quality Services. And here’s the official resource if you want to continue learning: DQS Knowledge Bases and Domains
Awesome Blog Posts about DQS written by fine Community folks: