System degrades after 49.71 days

From: Lockdesign Ltd (Ltd)_at_discussions.microsoft.com)
Date: 11/19/04

  • Next message: Hugo Kornelis: "Re: query question" 
    Date: Fri, 19 Nov 2004 01:13:09 -0800

    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.

  • Next message: Hugo Kornelis: "Re: query question"

    Relevant Pages