Trying to figure this one out

Thread view:

Brent White - 09 Aug 2006 13:54 GMT

We have two servers, one running Tomcat 3 with a SQL Server 2000
Backend that has been working for just under three years. It's a
little slow, but it works. The operating system is WIndows 2000
Advanced Server, SQL Server 2000 Standard. It has dual 1.3GHz
processors and the database server is running the Microsoft SQL JDBC
drivers. Apache 1.3 is the webserver.

We are trying to move to a system that has dual 3.8GHz Xeon processors
on a Windows 2003 Server. It is also running SQL Server 2000 Standard
SP4 with Tomcat 5. Apache 2 is the webserver

We are scratching our heads why an identical database, identical Java
code and a faster processor is running slower. We have upgraded to a
trial version of JNetDirect 4 JDBC driver (JSQLConnect) and have
verified that it is installed correctly with our software vendors. The
webserver, Tomcat, and SQL Server all reside on each box, so it's not a
networking issue.

What seems to be happening is that the code is almost ignoring the
indices on the tables that we setup. Things that weren't out of order
on the 2000 box are now out of order on the 2003 box, and I can't help
but believe that the indexing issue is related to the performance
issue.

Our software vendors say it's something in setup, but I don't know
where to go and I'm not a Java programmer (I use VB and T-SQL almost
exclusively).

Can someone help me?

Reply to this Message

Luke Webber - 09 Aug 2006 23:11 GMT

> We have two servers, one running Tomcat 3 with a SQL Server 2000
> Backend that has been working for just under three years. It's a
[quoted text clipped - 25 lines]
>
> Can someone help me?

I've never used either of those drivers, but I've had good experiences
with the free jTDS driver. It seems to be the driver of choice for SQL
Server...

http://jtds.sourceforge.net/

But before you try it, you might want to make sure that there is nothing
different in your database setup. All you'd need is for a
frequently-used table to be missing an essential key, and you'd see
problems of this nature.

You might want to try some of the slow queries directly from the Query
Analyser and check the query plan.

Cheers,
Luke

Reply to this Message

Trying to figure this one out

Free Magazines