Documente Academic
Documente Profesional
Documente Cultură
Check the mapping of fields that support data staging and in data marts.
Check the correctness of surrogate keys that uniquely identify rows of data.
Check for data-type constraints of the fields present in staging and core
levels.
Check the data loading status and error messages after ETLs (extracts,
transformations, loads).
Look for string columns that are incorrectly left or right trimmed.
Make sure all tables and specified fields were loaded from source to staging.
Make sure data types and formats are as specified during database design.
Make sure every ETL session completed with only planned exceptions.
Verify all data cleansing, transformation, and error and exception handling.
Make sure target tables are correctly populated with all expected records, and
none were rejected.
Verify all dependencies among data-load workflowsincluding source-tostaging, staging-to-operational data store (ODS), and staging-to-data marts
have been properly defined.
Check all ETL error and exception log messages for correctable issues.
Load the database with peak expected production volumes to help ensure
that the volume of data can be loaded by the ETL process within the agreedon window.
Compare ETL loading times to loads performed with a smaller amount of data
to anticipate scalability issues. Compare the ETL processing times component
by component to pinpoint any areas of weakness.
Monitor the timing of the reject process, and consider how large volumes of
rejected data will be handled.
Make sure the functionality of the system meets the business specifications.
Look for the count of records in source tables and compare them with counts
in target tables, followed by analysis of rejected records.
Hardware is in place and has been configured correctly including ETL tool
architecture, source system connectivity, and business objects.