I think Host info should be it's own table. Then you can tie several checks back to one host (in the future if not at launch). I also am not sure what the output consists of but it seems that using variables you could feasibly have several output templates and tie many checks to one of those. Custom fields could be tied into one of the other tables if the type of data is consistent with that table or you could keep it completely separate.
Schedule should definitely be it's own table because of the possible size/complexity of the data. I am not a database designer though. Take it for what you will. Jason Passow Network Administrator Mississippi Welders Supply http://www.mwsco.com (http://www.mwsco.com) [email protected] (mailto:[email protected]) ph: (507) 494-5178 fax: (507) 454-8104 -------------------------------------------------------------------------------- From: Dirk Bulinckx [mailto:[email protected]] To: Servers Alive Discussion List [mailto:[email protected]] Sent: Fri, 30 Nov 2012 10:30:20 -0600 Subject: [SA-list] Servers Alive's database back-end Some time ago it seemed to be a hot-topic to have a database backend for Servers Alive opposed to having a flat-text file like we have now. We are currently working on such a db backend (and no you won't need a SQL server or mySQL or Oracle server to run SA, SA will have its own simple build-in DB with option to use a big db system too). Having this db backend will give us more management options too so we think that this is a good thing to do. BUT as always we're faced with some open questions. Internaly (in SA I mean) we store the info of an entry is several large chuncks of data host info check info alerts info output info schedule info custom fields info In the db we could have one large table that combined host, check, output, schedule , custom fields And a "linked" table for the alerts (as you have several alerts per entry) This would mean at least something like 50 fields in one table OR we could have a table for host info check info output info schedule info custom fields info (and ofcourse for the alerts) (where for each host-record you would have 1 check record, 1 output record, 1 schedule record, 1 custom fields record) I can see pro's and cons for both systems. I would like to get some info/feedback from our users on how they would prefer this and why :-) Dirk Bulinckx Servers Alive - http://www.woodstone.nu (http://www.woodstone.nu) StellarDNS (DNS Hosting) - http://www.stellardns.com (http://www.stellardns.com) 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.
