Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 17895 Source: MSSQLSERVER
CPU time stamp frequency has changed from <number> to <number> ticks per milisecond. The new frequency will be used.
|English: This information is only available to subscribers. An example of English, please!|
According to ME931279 this issue occurs because CPU frequencies are changed when you use CPU stepping, AMD Cool'n'Quiet technology or other power schemes (usually applicable to desktop operating systems). SQL Server 2005 uses the high-resolution CPU counter to provide microsecond timing capabilities. If CPU frequencies are changed to conserve energy and reduce heat output, calculated durations may be incorrect. See the Microsoft PSS SQL Support Blog for details and ME931279 for one suggested workaround (it may work for fully blown SQL 2005 but not for the Express version running on regular desktops or laptops).
|Private comment: Subscribers only. See example of private comment|
|Links: ME931279, Microsoft PSS SQL Support Blog|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated