/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Table Layout

10/22/2020 219 views

I am trying to gain an overall understanding and location as to where everything is.  I was given the list of tables here, but not all of these tables are currently used.  I am having to select all from each table to get an idea as to what is stored.  Would anyone happen to have an easy to read definition of each table? 

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

3

Use a tool like MySQL Workbench to connect to the database with the reporting user. That will allow you to browse the tables and view their structure. The database doesn't use external keys, so it's not possible to create a schema with automated tools. In general, however, I have found it very easy to navigate and view the relationships between tables. For instance, the HD_TICKET table includes columns for HD_QUEUE_ID, HD_CATEGORY_ID and these correspond to the HD_QUEUE table's ID column and the HD_CATEGORY table's ID column respectively.

Answered 10/23/2020 by: chucksteel
Red Belt

All Answers

-1

KACE has never published a schema, probably for two reasons, first you would need to keep it up to date and publish it with every release and second, KACE was designed so that we as users never really get to see what’s under the hood. If you are facing a specific challenge whereby you would like to know what table connects to which, then just ask here in ITNinja and those of us with more experience will do our best to guide and explain.

Answered 10/23/2020 by: Hobbsy
Red Belt

  • It's more so comments on the tables. It would be easier to understand what data is contained in each table.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ