Consultor Eletrônico



Kbase P166683: Unacceptable performance when running DataServer for MS SQL Server 10.2B against MS SQL Server 2008
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   25/05/2010
Status: Unverified

SYMPTOM(s):

Unacceptable performance when running DataServer for MS SQL Server 10.2B against MS SQL Server 2008

Starting application can take up to 2 minutes

Performance issue is observed when using OpenEdge 10.2B ODBC Wire Protocol Driver for MS SQL Server (version 6.00.00.37)

Performance issue does not occur when using OpenEdge 10.2A ODBC Wire Protocol Driver for MS SQL Server (version 5.30.00.54)

Problem occurs whether using a schema holder generated in OpenEdge 10.2A or OpenEdge 10.2B

FACT(s) (Environment):

No problems encountered when running OpenEdge 10.2A
Same code, database schema, schema holder etc. are used when testing in OpenEdge 10.2A or OpenEdge 10.2B
OpenEdge 10.2B
Windows
MS SQL Server 2008

CHANGE:

Upgraded to OpenEdge 10.2B

CAUSE:

The problem is caused by a limitation in the DataDirect ODBC driver. The ODBC driver requires additional processing is required to support the new MS SQL Server 2008 date / time data types; this is experienced as additional SQL statements executing against the MS SQL Server database. For example:

SELECT DATA_TYPE,DATETIME_PRECISION FROM INFORMATION_SCHEMA.COLUMNS WHERE COLUMN_NAME='cust-num' AND ((TABLE_SCHEMA='mb' AND TABLE_NAME='dbo'))

The number of queries executed can vary depending on the number of fields in the table.

FIX:

If the use of the new MS SQL Server 2008 data types is not required then their use can be disabled via the Registry.

1) Run regedit

2) Backup the Registry

3) Go to the following location in the Registry:

32-bit Windows:
My Computer\HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\<YourDSNName>

64-bit Windows:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\<YourDSNName>

4) Right click >> New >> String value

5) Set the values to the following:

Value name: ReportDateTimeType
Value data: 0

6) Restart your OpenEdge session and re-test