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.

Chapter 7: The <strong>Data</strong><strong>Server</strong> Tutorial<br />

Primary/Clustered index as ROWID option, then one warning is generated with<br />

respect to both options. When both options are selected, this option becomes a<br />

secondary path in the search <strong>for</strong> the designated ROWID index. The primary and<br />

clustered selections associated with those options will take priority in ROWID<br />

selection as will the presence of a _PROGRESS_RECID column.<br />

10. Choose OK. <strong>OpenEdge</strong> displays a list of the data source objects that you can<br />

include in the schema holder, as shown:<br />

If you specified all wild cards as your table-selection criteria, the list might also<br />

include system-owned objects, which you do not have to include in the schema<br />

holder.<br />

11. Click the option appropriate to the action you want to per<strong>for</strong>m:<br />

• Select Some — Displays the Select by Pattern Match dialog box on which<br />

you can specify object in<strong>for</strong>mation used to select objects<br />

• Deselect Some — Displays the Deselect by Pattern Match dialog box on<br />

which you can specify object in<strong>for</strong>mation used to deselect objects<br />

You can also elect to select and deselect individual objects by clicking and<br />

double-clicking on an object. An asterisk appears next to an object that has been<br />

selected; double-click an object to remove the asterisk and identify that the object<br />

is now deselected.<br />

12. Choose OK after you have identified all the objects you want to include in the<br />

schema holder. The <strong>Data</strong><strong>Server</strong> reads in<strong>for</strong>mation about the objects that you<br />

select and loads their data definitions into the schema holder. The time that this<br />

process takes depends on the size and number of objects that you select.<br />

For each table, the <strong>Data</strong><strong>Server</strong> attempts to select an index to support the<br />

<strong>OpenEdge</strong> ROWID. If an appropriate index does not exist, the <strong>Data</strong><strong>Server</strong> issues<br />

the warning, Please check errors, warnings and messages in the file<br />

ds_upd.e. The ds_upd.e file lists the objects that do not support ROWID. You can<br />

change the <strong>Data</strong><strong>Server</strong>’s selection of an index to support ROWID by using the <strong>Data</strong><br />

Dictionary. See the “Defining the ROWID” section on page 311 <strong>for</strong> instructions.<br />

For additional in<strong>for</strong>mation, see the “Indexes and sorting” section on page 65.<br />

268 <strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong>

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

Saved successfully!

Ooh no, something went wrong!