We are implementing a testing framework, covering areas like mentioned in this SE article. But in addition, as part of unit testing (probably), we want to perform data contract testing.

The database is in SQL Server and the schema is managed through Visual Studio git code repository.

My question is are there best practices for data contract management that cover:

• where the data contract meta-data is stored
• how is the data contract meta-data accessed

In order to execute our data contract tests automatically, the management of the meta-data needs to be in an electronic form that is programmatically accessible - e.g. a SQL table. Also, we want to be able to include the information into word documents or PDFs becoming part of the system documentation.

We are implementing a testing framework, covering areas like mentioned in this SE article. But in addition, as part of unit testing (probably), we want to perform data contract testing.

The database is in SQL Server and the schema is managed through Visual Studio git code repository.

My question is are there best practices for data contract management that cover:

• where the data contract meta-data is stored
• how is the data contract meta-data accessed

In order to execute our data contract tests automatically, the management of the meta-data needs to be in an electronic form that is programmatically accessible - e.g. a SQL table. Also, we want to be able to include the information into word documents or PDFs becoming part of the system documentation.