Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 17895 Source: MSSQLSERVER

Source
Level
Description
CPU time stamp frequency has changed from <number> to <number> ticks per milisecond. The new frequency will be used.
Comments
 
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).

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...