Kbase P99212: Using MS SQL Server DataServer, application is 50% slower in OpenEdge 10.0B than in Progress 9.1D
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/12/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
OpenEdge 10.0B
MS SQL DataServer
SYMPTOM(s):
DataServer for Microsoft SQL Server application is 50% slower after migrating to OpenEdge 10.0B
Performances are much slower when adding the FIELDS statement
Schema holder has been built by loading the .df file created in 9.1D in an empty OpenEdge 10.0B database.
Using the OpenEdge 10.0B SQL Server Wire Protocol ODBC driver
Using the same connection parameters
CHANGE:
Migrating from Progress 9.1D to OpenEdge 10.0B
CAUSE:
The schema holder has not been rebuilt by using the the 'Create DataServer Schema' tool in the Data Administration.
OpenEdge 10.0B includes the following new features that provide additional support for improving the performance of OpenEdge DataServer for Microsoft SQL Server applications:
o Connection Pooling
o Firehose and Fast Forward-Only Cursors
o Monitoring cursor and connection use
In order to take advantage of the new features,the schema holder has to be rebuilt, loading a schema holder (.df) from a previous version is not enough. The reason is that there is a MISC field that needs to be populated by the Data Administration, this MISC field population is not done if a dump and reload is performed.
FIX:
Rebuild the schema holder.
See Solution P23300 for further information about how to create a schema holder for MS SQL Server.