Understanding the database schema is the key to building a custom report for EdgeSight. In this article you will learn about important tables and views as well as the relationship between them. This article explains the purpose and layout key tables in the EdgeSight database schema as well as the relationships between them.
As you may know, EdgeSight manages devices in companies and departments to represent an organizational structure. The corresponding tables are called company and dept. Every company is represented (among others) by a unique id (compid) and a name (name) contained in the corresponding fields. Departments are stored in the table dept where a unique id (compid), the name (name), the parent department (path) and the id if the corresponding company (compid) are the most important fields.
To learn more and to read the entire article at its source, please refer to the following page, Building Custom EdgeSight Reports Part 2 - The Database- Nicholas Dille
Sponsored Link: http://www.unitrends.com/free-backup/?src=dabcc