13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Verifying a schema holder<br />

Verifying a schema holder<br />

The Verify Table Definition utility allows you to verify that the schema holder <strong>for</strong> your data<br />

source matches the data definitions in the data source. For example, if you delete the customer<br />

table from the data source but not from the schema holder, this utility reports that the schema<br />

holder contains an orphaned object. You can verify the schema in<strong>for</strong>mation in a single table or<br />

from multiple tables, and then choose to update the tables so that the schema in<strong>for</strong>mation<br />

matches the data source definitions.<br />

The Verify Table Definition utility reads the definitions in the data source and compares them<br />

to the in<strong>for</strong>mation in the schema holder. It reports the differences that it finds and their degree<br />

of severity. These are the categories of differences and how they impact your database<br />

applications:<br />

• Minor — These differences have no impact on the usability of your application.<br />

• Retained — These differences cannot be corrected by the Update/Add utility, hence the<br />

term “retained.” You must determine how severely they impact your application and<br />

change the data definitions either in the schema holder using the <strong>Data</strong> Dictionary or in the<br />

data source.<br />

• Severe — These differences might cause your application to malfunction. When the<br />

Verify utility detects severe differences, it automatically updates the schema holder to<br />

solve the discrepancies by adjusting the schema-image in<strong>for</strong>mation in the schema holder<br />

to match the data source definitions. Severe differences in definitions that the <strong>Data</strong><strong>Server</strong><br />

uses internally also cause the schema holder to be updated.<br />

Table 7–4 lists the differences that the Verify Table Definition utility detects.<br />

Table 7–4: Verify utility report (1 of 2)<br />

<strong>Data</strong>base object Difference Category<br />

Table Description Retained<br />

Table Foreign type Severe<br />

Table Name in <strong>OpenEdge</strong> Retained<br />

Table ROWID index Retained<br />

Index Active Minor<br />

Index Description Retained<br />

Index Name in <strong>OpenEdge</strong> Retained<br />

Index Unique Retained 1<br />

Index field Abbreviated Minor<br />

Index field Ascending Severe<br />

Index field Order Severe<br />

Field Case sensitivity Retained<br />

7–13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!