January 25, 2010 at 6:18 am
Hello Everyone
I know this topic can be very vague, but I am running out of areas to investigate. I have one SQL 2000 box that will not hold a connection. I.E... If you connect via QA, in about 30 seconds, you will have to refresh the object explorer. If you take too long in writing a query, you will receive an error message stating the connection is broken, and you will have to try and refresh the database in object explorer.
This is running on a VM. I am not fond of that, but I did not set that up.
Can anyone suggest some places that I could look. I figure that may be easier that trying to tell you what I have already attempted. I may have overlooked some things as well. So I am not at all worried about covering that ground again. You may suggest something that I missed, or overlooked.
There is nothing in the Event Logs or the SQL logs that show anything out of the ordinary or strange behavior. The processor is running at a mere 2%. I have set the connection timeout up to 3600 seconds, but it still drops after approx 30 seconds.
Thanks in advance for your help and suggestions
Andrew SQLDBA
January 26, 2010 at 6:43 am
What about Enterprise Manager -->Tools --> Options --Advanced Tab -> Login Timeout?
Even as a mother protects with her life
Her child, her only child,
So with a boundless heart
Should one cherish all living beings;
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply