Try OpenEdge Now
skip to main content
DataServer for Microsoft SQL Server
The DataServer Tutorial : Verifying a schema holder
 

Verifying a schema holder

The Verify Table Definition utility allows you to verify that the schema holder for your data source matches the data definitions in the data source. For example, if you delete the customer table from the data source but not from the schema holder, this utility reports that the schema holder contains an orphaned object. You can verify the schema information in a single table or from multiple tables, and then choose to update the tables so that the schema information matches the data source definitions.
The Verify Table Definition utility reads the definitions in the data source and compares them to the information in the schema holder. It reports the differences that it finds and their degree of severity. These are the categories of differences and how they impact your database applications:
*Minor — These differences have no impact on the usability of your application.
*Retained — These differences cannot be corrected by the Update/Add utility, hence the term "retained." You must determine how severely they impact your application and change the data definitions either in the schema holder using the Data Dictionary or in the data source.
*Severe — These differences might cause your application to malfunction. When the Verify utility detects severe differences, it automatically updates the schema holder to solve the discrepancies by adjusting the schema-image information in the schema holder to match the data source definitions. Severe differences in definitions that the DataServer uses internally also cause the schema holder to be updated.
The following table lists the differences that the Verify Table Definition utility detects.
Table 54. Verify utility report
Database object
Difference
Category
Table
Description1
Retained
Table
Foreign type
Severe
Table
Name in OpenEdge
Retained
Table
ROWID index
Retained
Index
Active
Minor
Index
Description2
Retained
Index
Name in OpenEdge
Retained
Index
Unique
Retained3
Index field
Abbreviated
Minor
Index field
Ascending
Severe
Index field
Order
Severe
Field
Case sensitivity
Retained
Field
Decimals
Retained4
Field
Description5
Retained
Field
Extent
Severe
Field
Initial value
Retained6
Field
Mandatory
Retained
Field
Name in OpenEdge
Retained
Field
Order
Retained
Field
OpenEdge data type
Retained7
Field
OpenEdge format
Retained8
Field
Shadow-column Name
Severe
1 The differences in descriptions between OpenEdge and MS SQL Server is not captured during the verification process because MS SQL Server, unlike OpenEdge, does not store descriptions for tables, fields, and indexes.

2 The differences in descriptions between OpenEdge and MS SQL Server is not captured during the verification process because MS SQL Server, unlike OpenEdge, does not store descriptions for tables, fields, and indexes.

3 When you update an index, it is identified as unique if it was defined as unique in the data source or the schema holder.

4 If the corresponding information in the data source is incompatible with the information in the schema holder, the affected fields are not updated. For example, if the data source data type is decimal and the OpenEdge data type is CHARACTER, the data type information is not updated.

5 The differences in descriptions between OpenEdge and MS SQL Server is not captured during the verification process because MS SQL Server, unlike OpenEdge, does not store descriptions for tables, fields, and indexes.

6 If the corresponding information in the data source is incompatible with the information in the schema holder, the affected fields are not updated. For example, if the data source data type is decimal and the OpenEdge data type is CHARACTER, the data type information is not updated.

7 If the corresponding information in the data source is incompatible with the information in the schema holder, the affected fields are not updated. For example, if the data source data type is decimal and the OpenEdge data type is CHARACTER, the data type information is not updated.

8 If the corresponding information in the data source is incompatible with the information in the schema holder, the affected fields are not updated. For example, if the data source data type is decimal and the OpenEdge data type is CHARACTER, the data type information is not updated.

* Verifying a table