Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. Repositories
  4. XML Data Source
  5. Tests for XML Data Sources
  6. Connections
  7. Expressions
  8. Table Pairs
  9. Tests for Table Pairs
  10. Single-Table Constraints
  11. Tests for Single-Table Constraints
  12. Examples of Tests from Spreadsheets
  13. SQL Views
  14. Lookup Views
  15. Join Views
  16. Aggregate Views
  17. Business Intelligence and Reporting Tools Reports
  18. Dashboards
  19. DVOCmd Command Line Program
  20. Troubleshooting
  21. Appendix A: Datatype Reference
  22. Appendix B: Reporting Views
  23. Appendix C: Metadata Import Syntax
  24. Appendix D: Jasper Reports
  25. Appendix E: Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Primary Key File

Primary Key File

To use a table comparison to generate value and outer value tests for a table pair, you must specify the primary keys for both tables. If a relational table has a composite primary key or if a flat file does not have a column header, you can create a primary key file that specifies the primary key for the relational table or flat file.
In the Data Validation Client, you can select one column as the primary key for each table in a table pair. If the primary key of a relational data source is a composite primary key, you must create a primary key file that specifies all columns that comprise the primary key.
If a flat file does not contain column headers, then you must create a primary key file that specifies the column that is the primary key for the flat file. If the primary key is a composite key, then you can specify all columns that comprise the primary key.
The file must contain the name of the flat file or table and the primary key separated by comma.
For example:
flatfile_dictionary_10rows,FIELD1
To specify multiple columns of a composite primary key, enter each column on a new line.
For example:
flatfile_dictionary_10rows,FIELD1
flatfile_dictionary_10rows,FIELD2
flatfile_dictionary_10rows_str,FIELD1

0 COMMENTS

We’d like to hear from you!