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 />

Table 53: Generate Delta.sql <strong>OpenEdge</strong> to MSS utility (3 of 3)<br />

Interface element 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 — Use the value of<br />

the _<strong>for</strong>mat field in the _field<br />

record. (default)<br />

If you select the 4GL Format<br />

option, you have an additional<br />

setting to define:<br />

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

is on by default to indicate that<br />

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

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

30 characters.<br />

Note: You cannot use the Expand<br />

x(8) to 30 setting with the Width<br />

option.<br />

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

Column. Trigger is selected by<br />

default. Computed Column is<br />

preferred as it offers greater reliability,<br />

but is only available <strong>for</strong> MS <strong>SQL</strong><br />

<strong>Server</strong> 2005 and later.<br />

3. Choose OK. The utility generates a delta.sql file and, optionally, a delta.df<br />

file.<br />

When this step is per<strong>for</strong>med <strong>for</strong> an MS <strong>SQL</strong> <strong>Server</strong> <strong>Data</strong><strong>Server</strong>, and the<br />

incremental update procedure includes changing an existing field from INTEGER to<br />

INT64 in the schema holder, the <strong>Data</strong><strong>Server</strong> supports the update process through<br />

the ALTER TABLE ALTER COLUMN statement. If a column is part of an index, the<br />

incremental schema migration utility generates a script to drop any indexes that<br />

contain the column, change the column’s data type to BIGINT, and then re-adds<br />

the indexes. During this process, the utility uses the index definitions defined in<br />

the schema holder.<br />

4. After running the utility, you must apply the <strong>SQL</strong> that the utility generates to the<br />

MS <strong>SQL</strong> <strong>Server</strong> database and load the new delta.df file into the original schema<br />

holder so that it is synchronized with the modified MS <strong>SQL</strong> <strong>Server</strong> database.<br />

Note that if you updated an existing field from INTEGER to INT64 as described in<br />

Step 3 of this procedure, you also must confirm that none of the data is lost.<br />

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