Kbase P184639: Difference of behavior when using ROWID function through DataServer connection to MS SQL database.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/03/2011 |
|
Status: Unverified
SYMPTOM(s):
Difference of behavior when using ROWID function through DataServer connection to MS SQL database.
Getting 6117 error using ROWID against MS SQL Database.
SYSTEM ERROR: Assignment error. (6177)
Customer created MS SQL table outside of protomss.
Some tables work correctly when attempting to perform ROWID function.
Some tables don't work correctly when attempting to perform ROWID function.
Database created with protomss works correctly for all tables.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
Custom generation of field order may prevent proper functioning of operations such as ROWID.
Progress / OpenEdge is sensitive to the order of fields within the foreign database for some functions.
FIX:
If it is necessary to create a table definition using a tool other than the Data Dictionary / Data Administration tool then compare the table creation statements generated by Progress / OpenEdge and respect the field order defined by the protomss tool.
To generate the SQL statements that Progress / OpenEdge would use to create the MS SQL tables without actually creating the tables use the protomss function but de-select the Load SQL option.
1) Open the Data Dictionary / Data Administration tool.
2) Connect to the schema holder.
3) Select the DataServer menu.
4) Select the MS SQL Server Utilities option.
5) Select Schema Migration Tools.
6) Select OpenEdge DB to MS SQL Server.
7) Fill in the normal connection information.
8) De-Select the Load SQL option.
9) Complete the relevant additional options.
10) Click OK.
A <schema holder name>.sql file will be created in the working directory. This will contain the SQL statements that OpenEdge would use to create the table(s) within MS SQL.