RE: Advantages using 2005 JDBC Driver

Tech-Archive recommends: Fix windows errors by optimizing your registry

William,

Yes - our official stance is that we recommend you upgrade to the SQL Server 2005 JDBC driver.

Evan

--------------------
Thread-Topic: Advantages using 2005 JDBC Driver
thread-index: AcbxDuBOGjdawziOSWmLZVw/QsBtiA==
X-WBNR-Posting-Host: 203.222.183.3
From: =?Utf-8?B?V2lsbGlhbSBDYWk=?= <WilliamCai@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <E1D70271-AE0E-46C5-AD90-09D9B0F0DE52@xxxxxxxxxxxxx> <4TeC70hmGHA.5164@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Advantages using 2005 JDBC Driver
Date: Mon, 16 Oct 2006 03:36:02 -0700
Lines: 65
Message-ID: <4C1AB4DF-A316-4826-937D-BDF0B49B1FCE@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:8120
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

Evan,
I'm curious about what's Microsoft official suggestion regarding SQL 2005
JDBC driver issue. So can I understand that way Microsoft encourages
customers upgrade to 2005 JDBC driver? :-)

Thanks,
William

"Evan T. Basalik (MSFT)" wrote:

In my opinion, there are several good reasons to upgrade to the SQL 2005 JDBC driver:

1) Based on internal performance testing, the 2005 driver is faster
2) The 2005 driver supports both SQL Server 2000 and SQL Server 2005, while the SQL 2000 JDBC driver only supports SQL Server 2000
3) The 2005 driver is 100% Microsoft supported and is being actively developed within the SQL Server team

Evan

--------------------
Thread-Topic: Advantages using 2005 JDBC Driver
thread-index: AcaZ9wQpenna4T1dR8KOzyBuIX8HIg==
X-WBNR-Posting-Host: 198.187.195.144
From: =?Utf-8?B?UmljaGFyZA==?= <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Advantages using 2005 JDBC Driver
Date: Tue, 27 Jun 2006 07:36:03 -0700
Lines: 12
Message-ID: <E1D70271-AE0E-46C5-AD90-09D9B0F0DE52@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:7892
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

What are the major advantages of the 2005 driver over the 2000 driver?

We are running a active/passive db, with about 800 - 1000 database
connections.

We seem to be running low on available cursors. We get the server out
memory error about every three weeks. The number of available cursors,
decreases over this time frame. It seems to be related to the server out of
memory error. Any help?

About a third of our processes use the SelectMethod=Cursor. I think this
method is bad, considering out database load.



--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.





--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

.

Relevant Pages