Re: Advantages using 2005 JDBC Driver

That bug is addressed in the hotfix from KB917054. If you are still facing the issue, feel free to open up a hotfix case with us and we can deliver the hotfix for
the CallableStatement issue.

Evan
--------------------
Thread-Topic: Advantages using 2005 JDBC Driver
thread-index: AcafhtG6p3Y+UUooTuy70FnNjmqzHA==
X-WBNR-Posting-Host: 199.67.138.42
From: =?Utf-8?B?SEVSTEFOSSBKVU5JT1I=?= <HERLANIJUNIOR@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <E1D70271-AE0E-46C5-AD90-09D9B0F0DE52@xxxxxxxxxxxxx> <4TeC70hmGHA.5164@xxxxxxxxxxxxxxxxxxxxx> <80710AB1-1FD6-
4CDD-A57E-0C38A181DFC5@xxxxxxxxxxxxx> <ePML70tmGHA.4992@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Advantages using 2005 JDBC Driver
Date: Tue, 4 Jul 2006 09:28:01 -0700
Lines: 111
Message-ID: <17975B29-9C5A-484B-8A6E-3A57C73F1E25@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
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:7915
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

Guys take care of using cursor options with 2005 driver version. In the link:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125329, there´s a bug report about this.

I´ve got one that removing the option cursor everthing start working fine !!!

Rgds.

HJR

"Angel Saenz-Badillos[MS]" wrote:

Hi Richard,

There have been cursor related improvements, take a look at
http://msdn2.microsoft.com/en-us/library/ms378405.aspx for more information.

As far as "bug fixes", the Jdbc 2005 driver uses a completely different code
base from the 2000 driver so the term bug fix does not really apply. You
will very likely not find Jdbc 2000 driver bugs surfacing on the 2005
driver, but you might well find differences in behavior and new issues.
Going forward we hope that the fact that Sql Server now owns this driver
makes this transition worth while.

For new projects using the 2005 jdbc driver is a no brainer. If you have a
2000 driver project that you are actively working on I would also recommend
that you look into porting it into the new driver for future supportability,
support on the 2000 driver for any issues you may find will not be great.

--
Angel Saenz-Badillos [MS] Data Programmability
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://blogs.msdn.com/angelsb/




"Richard" <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80710AB1-1FD6-4CDD-A57E-0C38A181DFC5@xxxxxxxxxxxxxxxx
Are there any cursor related improvements or bug fixes?

"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
Loading