Pro2 - Doc bug indicates all Source table indexes are applied to Target


Article Number000091379
EnvironmentProduct: OpenEdge Pro2
Version: 4.5, 4.6.x, 5.x
OS: All Supported Platforms
Question/Problem Description

The Pro2 User's Guide mentions that all of the indexes from the source table are copied to the target table when Pro2 creates the target.  This has not been true since Pro2 Version 4.5.

Following is the statement made in the Pro2 User's Guide which mentions this:

"By default, all index information from the source schema is brought over to the target database during Pro2 implementation, with the exception that any unique keys are created as non-unique.
The source side index information is not used by Pro2 and is not required. Dropping unused or unnecessary indices on the target side can optimize Pro2 performance."
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement NumberDefect ODIA-2238

Historically Pro2 setups would copy all indices over to the target tables, so this statement was true at one time.  In more recent versions of the product these index definitions are generated into a .SQL file as CREATE INDEX statements.  This SQL can then later be applied to the SQL target db in order to add the desired indexes to the target database.


None at this time.
Last Modified Date9/4/2018 6:05 PM

Did this article resolve your question/issue?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025