RE: [WhatsUp Forum] SQL Server

[Erik Amundson]

Title: Occasional Missed Checks....

I have seen an issue where excessive syslog traffic (like what you'd get from a firewall connected to the internet) will cause SQL to hit 100%...I'm still working on figuring a fix for that one...   It would be an interesting to see IPSWITCH make the syslogging feature a lot more robust to handle something like this.  Ideas are to queue messages and do 'bulk inserts' of some kind into the DB instead of an insert for every message (of course, I'm only guessing this is how it's done now), or to allow a different type of passive-monitor to be setup that would allow for treating the syslog entries for that device differently.  This has got to be a problem on larger networks, particularily those connected to the Internet...    Erik Amundson A+, N+, CCNA, CCNP IT and Network Manager Open Access Technology Int'l, Inc. Phone (763) 201-2005 Fax (763) 553-2813 mailto:[EMAIL PROTECTED]   CONFIDENTIAL INFORMATION:  This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc.  Do not copy or distribute without the prior written consent of OATI.  If you are not a named recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic.   From: Steve Pope [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 12:05 PM To: WhatsUp_Forum@list.ipswitch.com Subject: [WhatsUp Forum] SQL Server Has anyone had an issue were SQL server runs at 100% CPU continually?   This is on a SQL server with a second instance of SQL running only for WUP.