Add matching knowledge to a knowledge base in DQS

-
A matching knowledge can be useful when building and maintaining unique, unduplicated
lists as Customers, Products, and Suppliers. You can use a DQS knowledge base to maintain unduplicated lists of Suppliers for example, by building a DQS knowledge base and setting up a DQS Matching Policy. During a matching activity, DQS evaluates the matching rules setup in the Matching Policy against the records being processed. It then provides a matching score for each record. If the matching score is greater than the minimum matching score configured then the two records are considered matches.

Create a matching policy
Follow the steps below to create a matching policy.
  • Open the Data Quality Services client and connect to the DQS instance
  • Click on Open Knowledge Base button from the Knowledge Base Management section
  • Select Suppliers from the Knowledge Base list
  • Click on Matching Policy under the Select Activity list, then click Next
  • Select Excel file from the Data Source drop-down list
  • Browse and select the SuppliersDomain.xlsx file
  • Select the SupplierforMatchingPolicy worksheet from the Worksheet drop-down list
  • Under the Mappings section, select SupplierName (nvarchar) from the Source Column drop-down list, then select SupplierName from the Domain drop-down list in the corresponding row. Click Next
  • Click the Create A Matching Rule icon on the menu bar
  • Type a name and description for the Matching Rule
  • Set the Min. matching score 
  • Under Rule Editor add SupplierName, then select Similarity from the Similarity dropdown list and set the Weight to 100%
  • Click the Start button to preview the matching results
  • Click Next, then click Finish













To add matching knowledge to a knowledge base, follow the steps below.
  • To add matching knowledge to a knowledge base, follow the steps below
  • Click on New Data Quality Project button from the Data Quality Projects section
  • Type a name and description for the Data Quality Project
  • Select Suppliers from the Use Knowledge Base drop-down list
  • Click on Matching Policy under the Select Activity list, then click Next
  • Select Excel File from the Data Source drop-down list
  • Browse and select the SuppliersDomain.xlsx Excel file containing the list of Suppliers to be matched
  • Select the worksheet containing the list of Suppliers to be matched from the Worksheet drop-down list
  • Under the Mappings section, select SupplierName (nvarchar) from the Source Column drop-down list, then select SupplierName from the Domain drop-down list in the corresponding row
  • Click Start to preview the matching results, then click Next
  • Select Excel file from the Destination Type drop-down list
  • Check the Survivorship Results check box, browse and select the Excel file to export
  • Click Finish

Comments

Post a Comment

Popular Posts

Enable logging for package execution in SSIS

-
Image
Logging can be enabled and used at design time and runtime. To begin logging, in the Visual  Studio menu select SSIS > Logging to open the Configure SSIS Logs window. In  the Containers section, select the Control Flow objects for logging—the overall package itself  and/or each of the individual tasks within the package. Then in the Providers and Logs tab,  under the Add A New Log > Provider Type, select where you want the logging to be saved to,  and click the Add button: After adding each of the Provider Types selected you want to log to, go to the Select the  Logs to Use for the Container section to set up the Connection in the Configuration column.  In the case of a Text file, select a file to write to. For SQL Server DB as the target,  simply select the target database. You are not limited to selecting only one target location for  the logging, multiple destinations can be added and they will all be wri...
Read more

Fix performance, connectivity, execution, and failed logic issues by using the debugger in SSIS

-
Image
Checking your execution results progress tab When you are testing your packages, and troubleshooting issues, the details of the execution  results can be found in the last tab of the package design environment. A point of possible  confusion can be how SSIS changes the name of this one tab depending on if the package is  executing or the package execution has been stopped. The last tab is labeled as follows: Execution Results tab When the package is not executing you can see the results of  the last run. Progress tab When a package execution is in-progress you can see the real-time  execution results. Once the package execution has been stopped, you can still see these  results under the Execution Results tab. Package execution reports in Management Studio Once you have a package executing successfully, you want to monitor and track its progress.  SQL Server Management Studio (SSMS) provides a very detailed, color-coded package execution...
Read more

Determine auditing or lineage requirements

-
One important criteria for success for any data warehouse project is to deliver data that is  trustworthy. Data can be trusted if you understand where it originates and what happens to  it as it goes through the extract, transform, and load (ETL) process. Data lineage provides an  audit trail of the data from its origin to its destination. Data lineage involves maintaining metadata repositories and auditing interactions with the  data as it flows from its origin to its destination. A metadata repository can include information  about the source and target systems, data types, data mappings, filters, business rules, transformations,  and aggregations applied to the data in the different data flows. Some ETL tools like SQL Server Integration Services (SSIS), provide a graphical representation  of data flows and keep track of the data lineage between source and destinations through  its internal metadata discovery and tracking mechanisms. SS...
Read more