We do not use SQL we use an access database.   I will address the second point. 
 We keep records of each and every check cycle for 1 week.   Anything older 
than 7 days but less than 30 is reduced to 30 minute intervals of checks + ALL 
down cycles.    After 30 days the timing is reduced to every 4 hours + all down 
cycles.    This allows to create graphs using return time or result values 
depending on the type of check (i.e. ping vs diskspace).    It allows to keep 
the database smaller by not have each and every cycle recorded.   We also keep 
SA debug logs for 30 days so if we discovered a problem that was not evident in 
the database (which hasn't happened yet) we could go back to the logs.   

Jason Passow
Mississippi Welders Supply
http://www.mwsco.com
[EMAIL PROTECTED]
ph: (507) 494-5178
fax: (507) 454-8104



--------------------------------------------------------------------------------

From: [EMAIL PROTECTED]
To: Servers Alive Discussion List [mailto:[EMAIL PROTECTED]
Sent: Wed, 02 Jul 2008 06:15:16 -0500
Subject: [SA-list] Logging to db


Does anyone use the option to send SA logs to a SQL database? If so: 


1. Do you have some sort of handy front end for it that you would be willing to 
share (for us non-SQL types)? 
2. How do you prevent it from constantly growing to monstrous proportions?

Thanks, 

Ian 
_________________________________
Ian K Gray
OEL IS - European Infrastructure Support
Tel: +44 1236 502661
Mob: +44 7881 518854
Ad eundum quo nemo ante iit 
______________________________________________________________________________


Any opinions expressed in this email are those of the individual and not 
necessarily of the Company. This email and any files transmitted with it, 
including replies and forwarded copies (which may contain alterations) 
subsequently transmitted from the Company are confidential and solely for the 
use of the intended recipient. It may contain material protected by legal 
privilege. If you are not the intended recipient or the person responsible for 
delivering to the intended recipient, be advised that you have received this 
email in error and that any use is strictly prohibited.
Please notify the sender immediately of the error and delete any copies of this 
message

Warning: Although the Company has taken reasonable precautions to ensure that 
no viruses are present in this e-mail, the Company cannot accept responsibility 
for any loss or damage arising from the use of this e-mail or attachments.


To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected] (mailto:[email protected])
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list.

Reply via email to