OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
The <strong>Data</strong><strong>Server</strong> Tutorial<br />
7–30<br />
Table 7–7: 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 primary<br />
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 the<br />
_<strong>for</strong>mat field in the _field record.<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 setting is<br />
on by default to indicate that the<br />
<strong>for</strong>mat <strong>for</strong> the character fields<br />
defined as x(8) will be created as 30<br />
characters.<br />
Note: You cannot use the Expand x(8)<br />
to 30 setting with the Width 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.<br />
3. Choose OK. The utility generates a delta.sql file and, optionally, a delta.df 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 incremental<br />
update procedure includes changing an existing field from INTEGER to INT64 in the schema<br />
holder, the <strong>Data</strong><strong>Server</strong> supports the update process through the ALTER TABLE ALTER<br />
COLUMN statement. If a column is part of an index, the incremental schema migration utility<br />
generates a script to drop any indexes that contain the column, change the column’s data<br />
type to BIGINT, and then re-adds the indexes. During this process, the utility uses the index<br />
definitions defined in the schema holder.<br />
4. After running the utility, you must apply the <strong>SQL</strong> that the utility generates to the MS <strong>SQL</strong><br />
<strong>Server</strong> database and load the new delta.df file into the original schema holder so that it<br />
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 Step 3 of<br />
this procedure, you also must confirm that none of the data is lost.<br />
The Incremental Schema Migration utility generates <strong>SQL</strong> that will create objects in the MS <strong>SQL</strong><br />
<strong>Server</strong> database that are compatible with <strong>OpenEdge</strong>. Table 7–8 shows that the utility creates the<br />
same objects as the <strong>OpenEdge</strong> DB to MS <strong>SQL</strong> <strong>Server</strong> migration utility.