July 13, 2004 at 2:24 pm
Hi, I have 1 NT server running SQL 7 and 1 Win2K server running SQL 7.
Both have very poor communication with m SQL Server 2000 database on Win2K. Any ideas?????
July 13, 2004 at 5:33 pm
Just that you should be more precise...
'I have 1 NT server running SQL 7 and 1 Win2K server running SQL 7' - seems fairly clear...
'Both have very poor communication with m SQL Server 2000 database on Win2K.' - is quite vague.
Poor communication ? How do you mean ?
And where is the 2K DB ?
You must be picking up bad user habits...
Cheers,
DB
The systems fine with no users loggged in. Can we keep it that way ?br>
July 13, 2004 at 6:00 pm
July 14, 2004 at 2:17 am
Without appearing to be clairvoyant I assume that all three DBs are on different machines. If that is the case, then when I have experienced the same issues with 'poor communications' - in that data from a linked database was accessed (most times), but very slowly - it came down to the same thing - the network.
Each time I came across this problem it was due to the use of Cisco switches, set to 10Mb half duplex on the SQL7 side, and 100Mb full duplex on the other.
I would suggest a good start is to look carefully at the network because once rectified the DBs communicate extremely well - even through a firewall.
July 14, 2004 at 3:56 pm
And then there was the time some contractors installed an Aeronet (radio lan comms) on the roof and picked the same ip as one of our SQL servers. Took a while to sort that one out. If you want "poor communications" between servers I can definitely reccommend that method.
The systems fine with no users loggged in. Can we keep it that way ?br>
July 15, 2004 at 7:04 am
Sorry I wasn't more clear. Everything has been looked at from the routers to the NIC cards.
1. All the databases are on seperate servers. All servers are setup as linked servers.
2. Here is my benchmark query:
select top 10 * from dca-server1.db_name.dbo.view_name (target db is SQL 2000)
3. Using query analyzer, if I connect to any SQL 2000 database and run this it takes 4 seconds. If I connect to a SQL 7 db and run this it takes 30 seconds.
I have checked the linked server setup and client and server connection utilities.
July 15, 2004 at 7:38 am
In Query Analyser, show the execution plan and client statistics for each query. Check that all servers are using the same indexes. Also check that the same number of packets and bytes are sent/received. This should confirm if you are comparing like with like. Does the query runs in 4 secs when run directly on the 2k server?
Have you PINGed the different servers from your PC? Are all the return times the same? If not, it is the network. Possibly, your link to the SQL 2K server is routed down a busy network link. Check the network route to the servers (sorry, can't remember the DOS command).
Hope this gives you some more ideas
Peter
July 15, 2004 at 8:12 am
the dos command is TRACERT followed by the ip address.
July 15, 2004 at 9:12 am
This may be of interest to you. We had a SQL 7 database (on NT 4) with a linked server to a SQL 2000 database (on W2K). The job on the SQL 7 box was pushing data to the SQL 2000 box and was very slow (10 minutes). I then created a link on the SQL 2000 box and was able to pull the same data in less than 1 minute. Perhaps just the newer OS and SQL are more efficient.
Linda
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply