Data Warehouse Defects

Below are descriptions of common defects that QuerySurge will find in your data warehouse projects. Using QuerySurge allows your team to implement a strong, repeatable regression testing strategy to avoid the adverse impact that any of these defects can cause your data warehouse and, ultimately, your Business Intelligence.

Issue
Missing Data

Description
Data that does not make it into the target database

Possible Causes
- Invalid or incorrect lookup table in the transformation logic - Bad data from the source database (Needs cleansing) - Invalid joins

Lookup table should which maps to Critic contains Hig - miss resulting in the targe this occurs on a key f missed and the entire

Truncation of Data

Data being lost by - Invalid field lengths on truncation of the data target database field - Transformation logic not taking into account field lengths from source Data types not set up correctly on target database Null source values not being transformed to correct target values Opposite of the Null Translation error. Field should be null but is populated with a non-null value or field should be populated, but with the wrong value Source data field not configured correctly Development team did not include the null translation in the transformation logic Development team incorrectly translated the source field for certain values

Source field value N truncated to New M field did not have the entire field.

Data Type Mismatch

Source data field was however, when initial VarChar.

Null Translation

A Source data field fo transformed to None However, the logic w in the target data fiel

Wrong Translation

Ex. 1) Target field sho the source field conta should be set to null Ex. 2) Target field sho value is an odd numb (This is a very basic e

Misplaced Data

Source data fields not being transformed to the correct target data field

Development team inadvertently mapped the source data field to the wrong target data field

A source data field w to target data field 'L development team in data field to 'First_Na

Extra Records

Records which should Development team did not be in the ETL are not include filter in their included in the ETL code Records which should Development team had be in the ETL are a filter in their code included in the ETL which should not have been there Testing sometimes can lead to finding holes in the transformation logic or realizing the logic is unclear Development team did not take into account special cases. For example international cities that contain special language specific characters might need to be dealt with in the ETL code

If a case has the dele and any data related any ETL

Not Enough Records

If a case was in a cert over to the data ware

Transformation Logic Errors/Holes

Ex. 1) Most cases may logic for a transforma cases (sometimes wit into any branches. Ho developers code han different (and possibl and the logic is chang Ex. 2) Tester and deve interpretations of the results in different va being re-written to b

Simple/Small Errors

Capitalization, spacing and other small errors

Development team did not add an additional space after a comma for populating the target field. Development team did not configure the sequence generator correctly resulting in records with a duplicate sequence number

Product names on a c comma and then a sp separated by a comm

Sequence Generator

Ensuring that the sequence number of reports are in the correct order is very important when processing follow-up reports or answering to an audit

Duplicate records in t up several sales trans report significantly

Undocumented Requirements

Find requirements that are understood but are not actually documented anywhere

Several of the members of the development team did not understand the understood undocumented requirements. Development team did not add the appropriate code to filter out duplicate records

There was a restrictio limited how certain re in mappings that wer but were not actually Occasionally it turns requirements are not

Duplicate Records

Duplicate records are two or more records that contain the same data Numbers that are not formatted to the correct decimal point or not rounded per specifications Data rows that get rejected due to data issues

Duplicate records in t up several sales trans report significantly

Numeric Field Precision

Development team The sales data did no rounded the numbers to and all sales were bei the wrong decimal point

Rejected Rows

Development team did not take into account data conditions that could break the ETL for a particular row

Missing data rows on issues with the end o