Clean data by using DQS knowledge

-
The DQS Client allows you to run a Data Quality Project to perform a Data Cleansing Activity. During the Data Cleansing Activity, DQS detects new, invalid, and correct values based on existing valid values, Synonyms and Term-Based Relations. The interactive data cleansing allows you to accept or reject suggestions and corrections that the DQS cleansing activity identified. Once all records have been processed, you can export the data cleansing results data and cleansing info.

To cleanse data using DQS knowledge follow the steps below.
  • Open the Data Quality Services client and connect to the DQS instance
  • 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 Cleansing 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 SuppliersforDataCleansing 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, then click Start to run the data cleansing analysis results. Upon completion click Next
  • Review the results under the Corrected and Suggested values in the Profiler tab as shown, then click Next
  • Review the records under each tab (Suggested, New, Invalid, Corrected, Correct). You can manage and review the data cleansing results. You can Approve or Reject the corrections or make your own corrections as seen. Click Next
  • To Export the cleansing results, select the Destination Type, Database or filename and Output Format options and click on the Export button, then Click Finish.














Comments

Post a Comment

Popular Posts

Install Master Data Services (MDS)

-
Image
The installation of Master Data Services consists of three steps as follows: 1. Install required Windows roles and features 2. Install Master Data Services from the SQL Server installation media 3. Configure Master Data Services from the MDS Configuration Manager Windows roles and features installation To install the Windows roles and features required for MDS, you can use Windows Server Manager  or through a PowerShell script. To start the Windows roles and features installation using  Windows Server Manager follow these steps: 1. Open Server Manager and click on Manage on the menu bar, then click Add Roles and  Features from the drop-down menu options to launch the Add Roles and Features  Wizard. 2. On the Select installation type window, select the “Role-based or feature-based installation”  option as shown and click Next. 3. On the Select destination server window, click the checkbox for the “Select a server  from the server pool” optio
Read more

Non-blocking, semi-blocking, and blocking transforms in SSIS

-
Not all Data Flow transforms are created equal. In fact, some are much faster and require a  lot less memory (non-blocking transforms). Others are slower while consuming much more  memory (blocking transforms), and some are in between (semi-blocking transforms). We don’t  always have a choice if we need to use a certain transform to do a certain specified task, but  it is good to know the differences between these types of transforms so that we can better  understand performance and resource utilization issues. Synchronous and asynchronous There is another related aspect about Data Flow transforms, which is their ability to quickly  process a row as they are coming into the transform, independently of any other rows that  came before or after (synchronous transforms). The other type of transform needs to be  dependent on some or all of the rows that come before and after (asynchronous transforms). On the whole, non-blocking transforms are also synchronous, thus are fast and
Read more

Design an appropriate storage solution, including hardware, disk, and file layout

-
Image
The data warehouse storage’s performance can be measured by  analyzing the time it takes for read and write operations to complete, known as latency , and by  analyzing how much data volume it can read or write in each time frame, known as throughput .  High latency and low throughput can be an indication of an improper selection for the  storage infrastructure or incorrect hardware and software configurations. Performance of a storage subsystem can  be estimated based on several criteria: Volume of data Rate of change and growth of the data Data retention policy Number of concurrent users Typical workloads expected Two important metrics associated with storage are throughput and Input/Output Per  Second (IOPS) . Throughput is a measure of the amount of data that can be transferred in a  period. This is typically measured in megabytes or gigabytes per second. IOPS is the number of  I/O read or write operations that can complete in a second.  It is important
Read more