Hi, Laura. I am running MS SQL Server 7.0 on an NT 4.0 server SP6a. Over a period of time, the active TCP connections build up and no further connections are able to be made to the server. I have confirmed that SQL Server is up and running and there are no active threads or jobs in SQL. I can open Enterprise Manager on the console and run queries. Additionally, I can continue to initiate and execute queries remotely. My question is: How can I tweak the server to clear orphan queries on that server?
The Windows default for maintaining a TCP connection open in a TIME_WAIT state is four minutes, which may be too long for your environments' needs. Refer to KB article
TCP/IP and NBT Configuration parameters for Windows 2000 or Windows NT
for information on modifying TCP parameters, especially the "TCPTimedWaitDelay" setting, which can be reduced as low as five seconds. All usual disclaimers about registry editing and testing changes before implementing them in a production environment apply.
Dig deeper on Windows File Management
Active Directory expert Laura E. Hunter offers some advice for changing the IP addresses of domain controllers.continue reading
An admin has two domains and two Active Directories. He wants to know how to join the Active Directories so that internal staff can access both, but ...continue reading
A Windows administrator moving from Windows Server 2003 to Windows Server 2003 R2 wants to perform a restore of a previous server to a new one ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.