Windows 2003 Server (Any Edition) May Hang After Installing SQL 2008 or 2005 SP3

Windows 2003 running SQL Server 2005 SP3 and SQL Server 2008 uses mmtimer (Multimedia) timer rather than the RDTSC timer, which changes the clock granularity from the default to 1ms (1 millisecond). This change may result in clock-drift or an unresponsive server if the server uses enhanced power management technologies that change CPU frequencies.

The issue may occur using (though not necessarily limited to) the following:

• AMD Cool'n'Quiet� Technology
• Enhanced Intel SpeedStep� Technology
• A variation of power schemes

 

A workaround to this issue is to revert the system clock timer resolution back to the default versus 1ms.  Given SQL is the process most likely associated with issue reports (any application can increase timer resolution via timeBeginPeriod)  please see the following KB article for a workaround to the SQL server configuration via Trace Flag -T8038:

 http://support.microsoft.com/kb/972767

Microsoft has observed this is issue only on HP ProLiant BL465c G5 Servers but it is conceivable other servers may be affected.

For the HP specific advisory on this issue please see:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02110402&dimid=1020231992&dicid=alr_apr10&jumpid=em_alerts/us/apr10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts 

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.