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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The <strong>Data</strong><strong>Server</strong> Tutorial<br />

7–12<br />

Check Default to <strong>OpenEdge</strong> DATETIME to automatically map MS <strong>SQL</strong> <strong>Server</strong> data<br />

types to the associated <strong>OpenEdge</strong> data type. If you have modified your client application<br />

to handle LOB data types, check Default to <strong>OpenEdge</strong> LOB to map the <strong>OpenEdge</strong> LOB<br />

data type to MS <strong>SQL</strong> <strong>Server</strong> VARBINARY (MAX), IMAGE and FILESTREAM data types. For<br />

more in<strong>for</strong>mation on mapping <strong>OpenEdge</strong> and MS <strong>SQL</strong> <strong>Server</strong> data types, see the “Support<br />

<strong>for</strong> <strong>OpenEdge</strong> ABL BLOB data type” section on page 2–30.<br />

3. Choose OK. A dialog box like the following example lists the objects and table<br />

in<strong>for</strong>mation that you have preselected:<br />

4. Select the objects that you want to update, then choose OK. When the update completes,<br />

you return to the <strong>Data</strong> Administration main window.<br />

When the update completes, you are reminded to check the ds_upd.e file. This file contains<br />

in<strong>for</strong>mation about the tables that did not support record IDs as well as other warnings.<br />

When you update a definition, <strong>OpenEdge</strong> overwrites the old definition with the new one based<br />

on the current data source object. It also preserves the <strong>OpenEdge</strong>-specific table in<strong>for</strong>mation. As<br />

a result, if you want to add a new column to a table in your data source and then update the<br />

definition, you do not have to re-enter all of the <strong>OpenEdge</strong>-specific in<strong>for</strong>mation <strong>for</strong> the<br />

previously existing columns (fields) in the definition.<br />

Note: When you update a table in the schema holder with the Update/Add Table Definitions<br />

utility, the in<strong>for</strong>mation <strong>for</strong> the user-defined ROWID is lost. You must reselect an index<br />

to support the ROWID.

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

Saved successfully!

Ooh no, something went wrong!