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.

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

Table 44: <strong>OpenEdge</strong> DB to MS <strong>SQL</strong> <strong>Server</strong> Conversion Advanced Options<br />

(2 of 2)<br />

Interface Elements Description<br />

For field widths use: When pushing fields to a <strong>for</strong>eign data<br />

source, you can select one of two<br />

primary field <strong>for</strong>mat options:<br />

• Width — Uses the value of the<br />

_width field in the _field record.<br />

• 4GL Format — Compiles with the<br />

current default width specified.<br />

(default)<br />

If you select the 4GL Format option,<br />

you have an additional setting to<br />

define:<br />

• Expand x(8) to 30 — This option is<br />

selected on by default to indicate<br />

that the <strong>for</strong>mat <strong>for</strong> the character<br />

fields defined as x(8) will be created<br />

as 30 characters.<br />

Note: You cannot use the Expand x(8)<br />

to 30 setting with the Width option.<br />

Apply Uniqueness as The Apply Uniqueness as option<br />

allows to you specify how uniqueness is<br />

defined. The default, Indexes, provides<br />

backward compatibility. The<br />

constraints option defines constraint<br />

definitions <strong>for</strong> uniqueness, but existing<br />

constraint definitions always take<br />

precedence over any constraint<br />

definition generation from this migration<br />

option.<br />

For Create RECID use Select either Trigger or Computed<br />

Column. Trigger is selected by default.<br />

Computed Column is preferred as it<br />

offers greater reliability, but is only<br />

available <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> 2005 and<br />

later. It comes with the restriction that<br />

you cannot place a server-based INSERT<br />

trigger on the table where the computed<br />

column option has been selected.<br />

Include Defaults The Include Defaults includes an<br />

Apply Default as option that allows you<br />

to specify if you want your defaults<br />

defined as Field Attributes (default) or<br />

constraints. The Field Attributes<br />

option provides backward compatibility.<br />

The Constraints option only defines<br />

constraint definitions if a constraint<br />

definition doesn't already exist. If you<br />

select Constraints, then after the<br />

migration, all the initial values defined <strong>for</strong><br />

migration become default constraint<br />

definitions on the server.<br />

256 <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!