-
SQL Server hotfix
I'm looking for additional information about SQL Server Hotfix 1037 or bug#
50000640. This is found at http://support.microsoft.com/kb/930484. This has
to do with SQL Server going 100% every 49.7 days for 15 minutes.
I have a similar issue that is happening when GetTickCount rolls over. I am
not sure it is SQL Server related. What it affects is network activity on the
server. The server has 6 NIC cards and is used to acquire data from various
plant equipment and distribute it to display stations. When this anomoly
occurrs, network packets are queues and in about 15 minutes all queued
packets are released. There are no event log entries from the system that
indicates there is an issue. My custom applications are crying about not
receiving data in a timely manner. After 15 minutes the condition clears, and
everything is good for another 49.7 days.
The reason I am looking for details, is that I am trying to determine if
this SQL Server bug might be involved with any type of network activity.
Apparently a worker thread is going into a hard loop doing something. I am
looking for a good reason and expectations of installing hotfix 1037.
At the next occurrance I plan on monitoring the system closing to see what
processes are using CPU.
Thanks for any help.
-
RE: SQL Server hotfix
Sorry I forgot to post the important stuff
SQL Server 2000 SP3a (no hotfixs) running on Windows Server 2003 SP2.
Running on a private network, no AD, no DOMAIN.
"meno" wrote:
> I'm looking for additional information about SQL Server Hotfix 1037 or bug#
> 50000640. This is found at http://support.microsoft.com/kb/930484. This has
> to do with SQL Server going 100% every 49.7 days for 15 minutes.
>
> I have a similar issue that is happening when GetTickCount rolls over. I am
> not sure it is SQL Server related. What it affects is network activity on the
> server. The server has 6 NIC cards and is used to acquire data from various
> plant equipment and distribute it to display stations. When this anomoly
> occurrs, network packets are queues and in about 15 minutes all queued
> packets are released. There are no event log entries from the system that
> indicates there is an issue. My custom applications are crying about not
> receiving data in a timely manner. After 15 minutes the condition clears, and
> everything is good for another 49.7 days.
>
> The reason I am looking for details, is that I am trying to determine if
> this SQL Server bug might be involved with any type of network activity.
> Apparently a worker thread is going into a hard loop doing something. I am
> looking for a good reason and expectations of installing hotfix 1037.
>
> At the next occurrance I plan on monitoring the system closing to see what
> processes are using CPU.
>
> Thanks for any help.