Re: System degrades after 49.71 days

From: Steve Kass (skass_at_drew.edu)
Date: 11/19/04


Date: Fri, 19 Nov 2004 10:55:48 -0500

Geoff,

This looks like a possibility:

  http://support.microsoft.com/default.aspx?scid=kb;en-us;823273

It may not be a problem specific to SQL Server, and there are a number
of other articles to check out here:

http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+49.7+days

Steve Kass
Drew University

Geoff Kell (Lockdesign Ltd) wrote:

>We have a SQL Server 7 database running on a Compaq Proliant ML370 under
>Windows 2000 Server.
>
>Normal operation has approximately 300-330 connections to the database.
>
>The system runs fine until after 49.71 days when we start to experience
>processes timing out their transactions. These processes had performed the
>exact same type of transactions without problem prior to the 49.71 days.
>
>The 49.71 days ties in with the number of milliseconds that may be held in a
>32 bit quantity. I have found reference to problems in this area for SQL
>Server 6.5 and the GetDate() function but nothing for SQL Server 7.
>
>It is interesting to note that this database was, until a year or so ago,
>running on a standard desktop style server under Windows NT 4 Server. Under
>this configuration we experienced no such problems at all. We upgraded to the
>Compaq server for increased resilience (dual network, power supply, etc). The
>problems we are experience are quite embarrassing as the reliability has
>fallen as we need to schedule reboots every 49 days. Since we run in a 24/7
>environment these restarts have quite an impact on our customers.
>
>Any advice/suggestions greatly appreciated.
>
>



Relevant Pages

  • Re: DB design, facilitates Double entries of internal transactions
    ... The single server is also ... transactions, even if just a pair of ID's/amounts, is still double entry. ... but I would tend to recommend SQL Server ... Stored Procedures and transaction control on the server. ...
    (microsoft.public.access.tablesdbdesign)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: migrating from wmsde to sql server
    ... Click Start, point to All Programs\Microsoft SQL Server, and then click ... then click New SQL Server Registration. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)

Loading