Feedback
Did this article resolve your question/issue?

   

Article

When using DataServer, should indexes be defined in OpenEdge or MS-SQL Server?

Information

 
TitleWhen using DataServer, should indexes be defined in OpenEdge or MS-SQL Server?
URL Namewhen-using-dataserver-should-indexes-be-defined-in-openedge-or-ms-sql-server
Article Number000154753
EnvironmentProduct: OpenEdge
Version: 11.x
OS: All supported platforms
Question/Problem Description
When using DataServer, should indexes be defined in OpenEdge or MS-SQL Server?
Where are indexes defined when accessing MS-SQL Data via DataServer?

 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
Indexes should be defined and maintained in MS SQL.  Per OpenEdge® Data Management: Initial Programming Considerations : Database design issues : Indexes and sorting:

"You create and maintain all indexes from within the MS SQL Server data source using native tools, rather than with the Data Dictionary. A data source index uses a logical pointer to the physical locations of table rows in order to sequence data access. You can add and drop indexes but you cannot use their names in queries. The data source alone ultimately decides when and how to use indexes; its decisions are not affected by the DataServer."
Workaround
Notes
Last Modified Date3/16/2020 5:13 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.