Determine appropriate use cases for a DQS Knowledge Base

-
Data Quality Services can be used for a wide variety of use cases to ensure that the data is suited for business usage. Data can be cleansed manually or computer-assisted by establishing matching and cleansing rules or by leveraging cloud-based services of reference data providers.

Incorrect or bad data is often a symptom of weak or lack of data validation rules during data entry. Other forms of inconsistent data can arise from data integration processes and data corruption. Bad, incorrect and inconsistent data create inefficiencies in the business processes and can lead to loss of revenue and increased operational costs. Bad data is often amplified during data analysis, reporting, data mining and data warehousing.

The main use cases for a DQS Knowledge Base involves the need for business users, information workers or IT professionals to create, maintain and execute data quality operations resulting from data incompleteness, inconsistency, inaccuracy, invalidity, duplication and nonconformity.

Data that is incomplete or incorrect can be cleansed using a DQS Knowledge Base by processing and analyzing how data conforms to the knowledge. The data steward can review, approve, reject or modify the computer-assisted process results. For example, incomplete data such as addresses can be enriched by reference data. Addresses missing or with invalid zip code values can be corrected with address validation services.

Fixing incorrect and non-standardized data is a common use case for DQS Knowledge Base. This is particularly important when integrating data from multiple sources. For example, different applications may store and display values for gender in multiple ways. Some of the most common values for gender may include ‘M’ for Male and ‘F’ for Female, others may store the word ‘Male’ or ‘Female’ or the values ‘0’ or ‘1’. These values can be automatically standardized by implementing term-based relationships or domain value synonyms in DQS. In addition, other rules can be put in place, such as null or blank values can be converted to ‘Unknown’ and values other than the ones expected above can be converted to ‘Other’.

In some cases, it can be hard to know all the different values that are expected for a domain. An example of this includes incorrect or alternate spellings of words. In this case, a Matching Policy can be created to programmatically correct misspelled domain values. Once a Matching Policy is defined, you can run a Data Quality Matching Activity Project with a new data set to match misspelled values based on the Matching Policy’s weight and similarity thresholds.

Comments

Post a Comment

Popular Posts

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

Implement additive, semi-additive, and non-additive measures

-
Additive Additive measures are numeric values that can be summed up by all the dimensions in the  fact table, for example the Sales Amount. These are the most common measures and they are  the easiest to understand and implement. Semi-additive Semi-additive measures are numeric values that can be summed up by some dimensions  in the fact table, but not all. In most cases, they can be aggregated by any other dimension  except time.  An example of a semi-additive measure is Account Balance. You can determine  the ending balance of an account at the end of a month, but adding up these monthly account  balances do not make sense. Semi-additive measures are usually found in fact tables that store  periodic snapshots of data. Non-additive Non-additive measures, as the name implies, are measures that cannot be summed up.  These measures include percentages such as Discount Percent, ratios such as Profit Margin, and  averages such as Average Unit Cost. Exam 70-767
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