November 21, 2007 at 2:36 am
I've been having the strangest problem regarding the SQL JDBC 1.0 Driver. I have a SQL Server 2005 database sitting on the SQL Server 2003 installation. Currently, for one of our high-availability apps, we have to have 2 IPs bound to the same machine, one is used as our standby IP, the other as the failover IP. I would expect the same performance regardless of which IP the application connects to. Unfortunately, this is not the case. For some bizarre reason, the Java code takes around 400ms to connect to the IP listed first, and 5000ms for the other IP. When I switch the order, the performance then switches. Has anyone had a similar problem, or have any advice?
Cheers,
Andrew
November 22, 2007 at 2:15 am
We have similar problem.
We tested driver version 1 and it ran very slowly (much slower that SQL 2000). We opened ticket in MS and they replied that we should validate the latest (not-yet-official) MS driver 2005 v1.2. The tests on this driver show the same degradation.
We are thinking currently about third party driver...
Any hints here guys?
MCP ID# 1115468 Ceritified Since 1998
MCP, MCSE, MCP+I, MCSE+I, MCSA,
MCDBA SQL7.0 SQL 2000, MCTS SQL 2005
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply