Functionally, to an admin, there isn't much difference. I would think that
for you using separate tables will provide flexiblity in the future for any
needed changes.
On Fri, Nov 30, 2012 at 11:30 AM, Dirk Bulinckx mailto:d...@woodstone.nu)> wrote:
Some time ago it seemed to be a hot-topic
PS don't take the lack of recent discussion as lack of desire. We are just
giving you time to implement without us asking when, when, when.
Jason Passow
Network Administrator
Mississippi Welders Supply
http://www.mwsco.com (http://www.mwsco.com)
jas...@mwsco.com (mailto:jas...@mwsco.com)
ph
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.
Servers Alive's database back-end
I would go with the first option.
Breaking the information into separate tables would help with the database
normalization
(http://en.wikibooks.org/wiki/Relational_Database_Design/Normalization
(http://en.wikibooks.org/wiki/Relational_Database_Design/Norm
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
