RE: SQL Timeouts

[Martin Blackstone]

Title: Message

Is this a 3rd party DB or one that has been written in house? I have experienced this issue twice in my career and each time it had nothing to do with HW or SW, but rather a poorly written/optimized DB. Who is in charge of creating and managing the DB? -----Original Message----- From: Paul Broomfield [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:50 AM To: NT System Admin Issues Subject: SQL Timeouts Hello,   One of our servers runs NT 4 and SQL 7.  Our Client machines (Win2k Pro) try to connect to the SQL server either via ODBC (in a VB app) or using Enterprise manager, they keep receiving intermittent “Timeout Expired” messages.  This didn’t happen a week ago, and AFAIK nothing has changed on the server or the client PCs.  I’ve tried restarts, SP, Hotfixes, reinstalling client software.   The client PCs are made up to Win2kPro SP2, Visual Studio 6 SP5 and SQL 2000 Client Tools Everything on the network is 100mb Cat 5   The odd thing is I installed a fresh copy of Win2k SP1, Visual Studio 6 (no SP) the user access our VB app and never gets a “Timeout Expired” error. Grrrrrr!.  Therefore I thought ahh perhaps then its SQL that’s causing the problems, so I ripped it off my machine but I still get the same error message.   I can’t see any problems with the server, web sites access the DB fine.   Any body have any ideas.   Thanks Paul http://www.sunbelt-software.com/ntsysadmin_list_charter.htm http://www.sunbelt-software.com/ntsysadmin_list_charter.htm