ODBC driver for SQL Server 2000
- From: Charles Zhang <CharlesZhang@xxxxxxxxxxxxxxxxx>
- Date: Tue, 06 Mar 2007 21:16:02 -0800
I have a server application that uses ODBC drivers to connect to databases.
When the number of parameters in a stored procedures reach a certain number such as 25, and named parameters are used and SQL Server 2000 ODBC driver is used to connect SQL Server 2000 databases, the server application crashed when calling ODBC APIs from time to time. I could not find a pattern to duplicate the crashes as yet.
If named parameters are NOT used, then the server application does not crash.
If SQL Native Client ODBC driver(ODBC driver from SQL Server 2005) is used to connect to SQL Server 2000 databases, the server application does not crash even named parameters are used.
I used other ODBC drivers to connect to Oracle databases using similar stored procedures, the server does not crash either.
From those facts, I believe some things are wrong with the SQL Server 2000 ODBC driver.
I have two questions:
1. Are there any newer SQL Server 2000 ODBC drivers?
The version of the ODBC driver for SQL Server 2000
installed on my computer is 2000.85.1117.00 dated Aug 4, 2004?
2. Are there any work around to get rid of this problem? I do not want the server application crash.
Thanks
Charles Zhang
.
- Follow-Ups:
- RE: ODBC driver for SQL Server 2000
- From: Walter Wang [MSFT]
- RE: ODBC driver for SQL Server 2000
- Prev by Date: Re: 32 bit ODBC in Win XP x64?
- Next by Date: RE: ODBC driver for SQL Server 2000
- Previous by thread: Re: sql*.h missing in MDAC 2.8 ?
- Next by thread: RE: ODBC driver for SQL Server 2000
- Index(es):
Relevant Pages
|