0 | ao_server_daemon_hosts | 1.0a100 | | AOServ Server Daemon Hosts | false | <code>ao_server_daemon_hosts</code> stores which hosts may connect to the AOServ Daemon on a server. |
1 | ao_servers | 1.0a100 | | AOServ Servers | false | The ao_servers table keeps track of all the servers that are running the AOServ distribution. |
2 | aoserv_permissions | 1.21 | | AOServ Permissions | true | <code>aoserv_permissions</code> lists all of the possible permissions in the AOServ Platform. |
3 | aoserv_protocols | 1.0a101 | | AOServ Protocols | true | <code>aoserv_protocols</code> keeps track of the different versions of the protocol
and what is available in that protocol. |
4 | aosh_commands | 1.0a100 | | AOSH Commands | true | <code>aosh_commands</code> stores the details about each command that may be used in the AO shell. |
5 | architectures | 1.0a100 | | Architectures | true | The architectures table provides all the possible computer architectures for the servers table. |
6 | backup_partitions | 1.0a100 | | Backup Partitions | false | The <code>backup_partitions</code> table stores the details of each backup location. |
7 | backup_reports | 1.0a101 | | Backup Reports | false | The <code>backup_reports</code> table stores the daily summary of backup system usage. |
8 | backup_retentions | 1.0a100 | | Backup Retentions | true | <code>backup_retentions</code> stores all of the possible backup retention times. |
9 | bank_accounts | 1.0a100 | | Bank Accounts | false | The bank_accounts table stores all the bank accounts we operate. |
10 | bank_transaction_types | 1.0a100 | | Bank Transaction Types | false | The bank_transaction_types table stores all the possible types of transactions for bank_transactions. |
11 | bank_transactions | 1.0a100 | | Bank Transactions | false | The bank_transactions table stores all the the transactions that have occured on a bank account. |
12 | banks | 1.0a100 | | Banks | false | The banks table stores information about each bank we deal with |
13 | blackhole_email_addresses | 1.0a100 | | Blackhole Email Addresses | false | The blackhole_email_addresses is a list of email addresses in which all email sent
to them is immediately discarded via /dev/null. |
14 | brands | 1.44 | | Brands | false | Each brand has separate website, packages, nameservers, and support |
15 | business_administrators | 1.0a100 | | Business Administrators | false | The business_administrators table stores details about the people who are allowed
to access the aoserv and aoweb utilities. |
16 | business_administrator_permissions | 1.21 | | Business Administrator Permissions | false | Grants administrative permissions. |
17 | business_profiles | 1.0a100 | | Business Profiles | false | The business_profiles stores all the old profile data for a business.
This is done so that old contacts may be used in case of an emergency. |
18 | businesses | 1.0a100 | | Businesses | false | The businesses table stores details about businesses |
19 | business_servers | 1.0a100 | | Business Servers | false | The business_servers table stores which servers may be accessed by which business.
A child business can only access a subset of the parent business' servers.
Only one entry per business is flagged as default. |
20 | country_codes | 1.0a100 | | Country Codes | true | The country_codes table contains all of the valid country codes.
This data was obtained from http://digitalid.verisign.com/ccodes.html |
21 | credit_card_processors | 1.29 | | Credit Card Processors | false | The credit_card_processors table stores all of the different credit card processing merchant accounts. |
22 | credit_card_transactions | 1.29 | | Credit Card Transactions | false | The credit_card_transactions table stores the complete history of credit card processor transactions. |
23 | credit_cards | 1.0a100 | | Credit Cards | false | The credit_cards table stores all of the client credit card information in an encrypted format. |
24 | Currency | 1.83.0 | | Currencies | true | The supported currencies. |
25 | cvs_repositories | 1.0a100 | | CVS Repositories | false | The <code>cvs_repositories</code> table stores the details of each CVSROOT |
26 | cyrus_imapd_binds | 1.81.10 | | Cyrus IMAPD Binds | false | The <code>cyrus_imapd_binds</code> table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be POP3, IMAP2, SIMAP, or SPOP3. |
27 | cyrus_imapd_servers | 1.81.10 | | Cyrus IMAPD Servers | false | The cyrus_imapd_servers table contains a list of all the Cyrus IMAPD servers. |
28 | disable_log | 1.0a100 | | Disable Log | false | The <code>disable_log</code> logs all the times things are disabled. |
29 | distro_file_types | 1.0a100 | | Distro File Types | false | The distro_file_types stores all of the possible file types. |
30 | distro_files | 1.0a100 | | Distro Files | false | The distro_files stores all of the file attributes in the templates. |
31 | distro_report_types | 1.70 | | Distro Report Types | false | The distro_report_types stores all of the possible report types. |
32 | dns_forbidden_zones | 1.0a100 | | DNS Forbidden Zones | true | <code>dns_forbidden_zones</code> stores all of the DNS zones that may not be hosted by the name servers |
33 | dns_records | 1.0a100 | | DNS Records | false | <code>dns_records</code> stores all of individual records of the name server. |
34 | dns_tlds | 1.0a100 | | DNS TLDs | true | <code>dns_tlds</code> stores all of the domains that are considered to be "top level domains". |
35 | dns_types | 1.0a100 | | DNS Types | true | <code>dns_types</code> stores all of the types of entries that may be placed in a line of a zone file. |
36 | dns_zones | 1.0a100 | | DNS Zones | false | <code>dns_zones</code> stores all of the DNS zones. |
37 | email_addresses | 1.0a100 | | Email Addresses | false | The email_addresses table stores a central pool of all email addresses. |
38 | email_attachment_blocks | 1.0a116 | | Email Attachment Blocks | false | The email_attachment_blocks table stores all attachment types that are currently blocked. |
39 | email_attachment_types | 1.0a116 | | Email Attachment Types | true | <code>email_attachment_types</code> stores all of the possible attachment extensions that may be blocked. |
40 | email_domains | 1.0a100 | | Email Domains | false | The email_domains table stores all the domains that the MTA responds to. |
41 | email_forwarding | 1.0a100 | | Email Forwarding | false | The email_forwarding sends email addresssed to email_addresses to another address. |
42 | email_list_addresses | 1.0a100 | | Email List Addresses | false | The email_list_addresses attaches the email_addresses to the email lists. |
43 | email_lists | 1.0a100 | | Email Lists | false | The email_lists table stores pointers to all the list files that are used for email. |
44 | email_pipe_addresses | 1.0a100 | | Email Pipe Addresses | false | The email_pipe_addresses attaches the email_addresses to the email pipes. |
45 | email_pipes | 1.0a100 | | Email Pipes | false | The email_pipes table stores pointers to all the processes that are used for direct delivery of email. |
46 | email_smtp_relay_types | 1.0a100 | | Email SMTP Relay Types | true | The email_smtp_relay_types table stores all the different types of SMTP rules. |
47 | email_smtp_relays | 1.0a100 | | Email SMTP Relays | false | The email_smtp_relays table stores the SMTP server access rules. |
48 | email_smtp_smart_host_domains | 1.57 | | Email SMTP Smart Host Domains | false | The email_smtp_smart_host_domains table stores optional per-domain settings for email_smtp_smart_hosts. |
49 | email_smtp_smart_hosts | 1.57 | | Email SMTP Smart Hosts | false | The email_smtp_smart_hosts table indicates a SMTP port is configured as a SmartHost for one or more servers. |
50 | email_sa_integration_modes | 1.0a120 | | Email SpamAssassin Integration Modes | true | The email_sa_integration_modes tables provides all the possible spam assassin itegration modes supported. |
51 | encryption_keys | 1.23 | | Encryption Keys | false | The encryption_keys table stores the list of GPG key ids on a per-business basis. |
52 | expense_categories | 1.0a100 | | Expense Categories | false | The expense_categories table is a lookup for bank_transactions, and is used to
organize expenditures for accounting purposes. |
53 | failover_file_log | 1.0a100 | | Failover File Log | false | The failover_file_log records statistics about each finished failover file replication. |
54 | failover_file_replications | 1.0a100 | | Failover File Replications | false | The failover_file_replications configures the replication of files from servers to failover servers. |
55 | failover_file_schedule | 1.0a100 | | Failover File Schedule | false | The failover_file_schedule controls when replications occur. |
56 | failover_mysql_replications | 1.28 | | Failover MySQL Replications | false | The failover_mysql_replications indicates a failover replication is using MySQL replication
for /var/lib/mysql/... instead of file-based replication. |
57 | file_backup_settings | 1.0a100 | | File Backup Settings | false | The <code>file_backup_settings</code> table overrides everything in the backup
system except <code>file_backup_devices</code>. |
58 | firewalld_zones | 1.81.0 | | Firewalld Zones | false | The <code>firewalld_zones</code> table defines all Firewall zones used on an AOServer. |
59 | ftp_guest_users | 1.0a100 | | FTP Guest Users | false | Each <code>linux_account</code> may optionally be a guest FTP user. A guest FTP user is restricted
to FTP access in their home directory. The passwd and group files are created such that any username
or group in the same business resolve to the correct text names. |
60 | httpd_binds | 1.0a100 | | Httpd Binds | false | The <code>httpd_binds</code> table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be HTTP or HTTPS. |
61 | httpd_jboss_sites | 1.0a100 | | Httpd JBoss Sites | false | <code>httpd_jboss_sites</code> ties httpd_sites to a jboss version to its httpd_shared_tomcat JVM. |
62 | httpd_jboss_versions | 1.0a100 | | Httpd JBoss Versions | true | <code>httpd_jboss_versions</code> is a lookup table containing information about different jboss versions. |
63 | httpd_jk_codes | 1.0a100 | | Httpd JK Codes | true | The httpd_jk_codes table contains all the possible mod_jk codes.
The codes must be unique for one httpd_sites when the site is used
in multiple httpd_servers. |
64 | httpd_jk_protocols | 1.0a100 | | Httpd JK Protocols | true | The httpd_jk_protocols table contains all of the possible protocols used by the mod_jk Apache module. |
65 | httpd_servers | 1.0a100 | | Httpd Servers | false | The httpd_servers table contains a list of all the Apache servers. |
66 | httpd_shared_tomcats | 1.0a100 | | Httpd Shared Tomcats | false | <code>httpd_shared_tomcats</code> stores information about the JVM shared by httpd_tomcat_shared_sites. |
67 | httpd_site_authenticated_locations | 1.18 | | Httpd Site Authenticated Locations | false | The <code>httpd_site_authenticated_locations</code> configured Apache basic
authentication using Location directives. |
68 | httpd_site_bind_headers | 1.81.15 | | Httpd Site Bind Headers | false | The <code>httpd_site_bind_headers</code> configures headers on httpd_site_binds. |
69 | RewriteRule | 1.81.21 | | Rewrite Rules | false | The per-VirtualHost set of RewriteRule. |
70 | httpd_site_binds | 1.0a100 | | Httpd Site Binds | false | The <code>httpd_site_binds</code> attaches httpd_sites to httpd_binds. |
71 | httpd_site_urls | 1.0a100 | | Httpd Site URLs | false | The <code>httpd_site_urls</code> stores the hostnames that a site will respond to. |
72 | httpd_sites | 1.0a100 | | Httpd Sites | false | The httpd_sites table stores all of the site names used in the
/www directory on servers. Each site name must be unique per
server. Also, for site portability, it is preferred that sites
remain unique between one set of servers. Such as AO Industries
will use unique names across all of its virtual servers, while
resellers may also choose to use unique names across their sets
of dedicated machines. |
73 | httpd_static_sites | 1.0a100 | | Httpd Static Sites | false | The <code>httpd_static_sites</code> stores the details of all sites that simply host static content only. |
74 | httpd_tomcat_contexts | 1.0a100 | | Httpd Tomcat Contexts | false | The <code>httpd_tomcat_contexts</code> stores the details of all contexts for all Tomcat sites. |
75 | httpd_tomcat_data_sources | 1.5 | | Httpd Tomcat Data Sources | false | The <code>httpd_tomcat_data_sources</code> stores the data sources on a per-context basis. |
76 | httpd_tomcat_parameters | 1.5 | | Httpd Tomcat Parameters | false | The <code>httpd_tomcat_parameters</code> stores the parameters on a per-context basis. |
77 | httpd_tomcat_site_jk_mounts | 1.81.6 | | Httpd Tomcat Site JK Mounts | false | The <code>httpd_tomcat_site_jk_mounts</code> stores the JkMount and JkUnMount settings for each Tomcat-based site. |
78 | httpd_tomcat_sites | 1.0a100 | | Httpd Tomcat Sites | false | The <code>httpd_tomcat_sites</code> stores the details of all sites based on the Tomcat servlet engine.
This includes JBoss, single instance Tomcats, and a Tomcat that runs in a shared Java VM. |
79 | httpd_tomcat_shared_sites | 1.0a100 | | Httpd Tomcat Shared Sites | false | <code>httpd_tomcat_shared_sites</code> ties the httpd_tomcat_site to its httpd_shared_tomcat JVM. |
80 | httpd_tomcat_std_sites | 1.0a100 | | Httpd Tomcat Std Sites | false | The <code>httpd_tomcat_std_sites</code> table stores the details for each site that
is self contained in its /www directory. |
81 | httpd_tomcat_versions | 1.0a100 | | Httpd Tomcat Versions | true | The <code>httpd_tomcat_versions</code> is a lookup of all the available versions of Tomcat. |
82 | httpd_workers | 1.0a100 | | Httpd Workers | false | The httpd_workers table contains all of the workers that are registered on each server. |
83 | ip_addresses | 1.0a100 | | IP Addresses | false | The ip_addresses table has an entry for every IP address hosted on our machines. |
84 | IpAddressMonitoring | 1.81.18 | | IP Address Monitoring | false | The monitoring configuration for ip_addresses |
85 | ip_reputation_limiter_limits | 1.66 | | IP Reputation Limiter Limits | false | The per-class limits for each IP Reputation Limiter. |
86 | ip_reputation_limiter_sets | 1.66 | | IP Reputation Limiter Sets | false | The sets for each IP Reputation Limiter. |
87 | ip_reputation_limiters | 1.66 | | IP Reputation Limiters | false | A network traffic limiter based established IP reputation. |
88 | ip_reputation_set_hosts | 1.65 | | IP Reputation Set Hosts | false | The per-host reputation for each IP Reputation Set. |
89 | ip_reputation_set_networks | 1.65 | | IP Reputation Set Networks | false | The per-network reputation for each IP Reputation Set. |
90 | ip_reputation_sets | 1.65 | | IP Reputation Sets | false | A set of IP reputation on a per-host and per-network basis. |
91 | languages | 1.44 | | Languages | true | The languages table provides all the possible languages for brands. |
92 | linux_acc_addresses | 1.0a100 | | Linux Account Addresses | false | The linux_acc_addresses table links email addresses to linux accounts. |
93 | linux_account_types | 1.0a100 | | Linux Account Types | true | The linux_account_types table stores all the different types of linux accounts. |
94 | linux_accounts | 1.0a100 | | Linux Accounts | false | The linux_accounts table stores all of the linux account info that is common to all machines. |
95 | linux_group_accounts | 1.0a100 | | Linux Group Accounts | false | The linux_group_accounts stores the alternate users for linux groups. |
96 | linux_group_types | 1.0a100 | | Linux Group Types | true | The linux_group_types table stores all the different types of linux groups. |
97 | linux_groups | 1.0a100 | | Linux Groups | false | The linux_groups table stores the details of each linux group that are common to every server. |
98 | linux_server_accounts | 1.0a100 | | Linux Server Accounts | false | The linux_server_accounts table contains the user configuration that is unique to each server. |
99 | linux_server_groups | 1.0a100 | | Linux Server Groups | false | The linux_server_groups table stores the details about the groups that exist on the servers. |
100 | majordomo_lists | 1.0a100 | | Majordomo Lists | false | The majordomo_lists table stores the details of each list in a majordomo_server. |
101 | majordomo_servers | 1.0a100 | | Majordomo Servers | false | The majordomo_servers table stores all the details for one domain of Majordomo hosting. |
102 | majordomo_versions | 1.0a100 | | Majordomo Versions | true | The majordomo_versions table contains a list of all the supported versions of the
Majordomo manages email list server. |
103 | master_hosts | 1.0a100 | | Master Hosts | false | <code>master_hosts</code> stores which hosts each user may connect from. |
104 | master_processes | 1.0a100 | | Master Processes | false | |
105 | master_server_stats | 1.0a100 | | Master Server Stats | false | |
106 | master_servers | 1.0a100 | | Master Servers | false | <code>master_servers</code> stores which servers each user may control. |
107 | master_users | 1.0a100 | | Master Users | false | <code>master_users</code> stores the authorization information for people that may access the master controller. |
108 | monthly_charges | 1.0a100 | | Monthly Charges | false | The monthly_charges table contains an entry for each transaction that is automatically charged each month. |
109 | mysql_databases | 1.0a100 | | MySQL Databases | false | The mysql_databases table stores the information about each MySQL database in the system. |
110 | mysql_db_users | 1.0a100 | | MySQL DB Users | false | The <code>mysql_db_users</code> table stores which <code>mysql_server_users</code> can access
which <code>mysql_databases</code>. The user permissions are also contained in each row. |
111 | mysql_server_users | 1.0a100 | | MySQL Server Users | false | The mysql_server_users table contains all the server-specific information about a mysql_user |
112 | mysql_servers | 1.4 | | MySQL Servers | false | The mysql_servers table stores the information about each MySQL instance in the system. |
113 | mysql_users | 1.0a100 | | MySQL Users | false | The mysql_users table stores all of the user info that is common for every MySQL server a user has
a MySQL user account on. The server specifics are stored in the mysql_server_users table. |
114 | net_bind_firewalld_zones | 1.81.0 | | Net Bind Firewalld Zones | false | Each port may be independently associated with a specific set of Firewalld Zones. |
115 | net_binds | 1.0a100 | | Net Binds | false | <code>net_binds</code> stores all of ports that should be bound to
by processes running on the servers. If any ports is bound to that
is not listed here, it may indicate a security violation. This
data is also used to open firewall ports. Each port may also be
periodically monitored for process reliability.
<p>
Four types of IP addresses exist:
</p>
<ol>
<li>wildcard - Processes bind to all available IP addresses on
the server. Monitoring may be performed from
anywhere, depending on firewall flags.</li>
<li>public - Processes bind to a public IP address. Monitoring
may be performed from the localhost or public
network, depending on firewall rules.</li>
<li>private - Processes bind to a private IP address. Monitoring
may be performed from the localhost or private
network, depending on firewall rules.</li>
<li>loopback - Processes bind internally in the server. Monitoring
may only be performed from localhost.</li>
</ol> |
116 | net_device_ids | 1.0a100 | | Net Device IDs | true | The net_device_ids contains all the network devices used on Linux servers. |
117 | net_devices | 1.0a100 | | Net Devices | false | The net_devices table contains each device used by Linux servers. |
118 | net_tcp_redirects | 1.0a111 | | Net TCP Redirects | false | The net_tcp_redirects table stores all of the xinetd redirect configurations. |
119 | notice_log | 1.0a100 | | Notice Log | false | The table notice_log contains information about any late or non-payment notices. |
120 | NoticeLog.balance | 1.83.0 | | Notice Log Balances | false | The per-currency balances for a NoticeLog. |
121 | notice_types | 1.0a100 | | Notice Types | true | The table notice_types provides lookup information for the notice_log table |
122 | operating_system_versions | 1.0a100 | | Operating System Versions | true | The operating_system_versions table provides all the supported versions of operating_systems. |
123 | operating_systems | 1.0a100 | | Operating Systems | true | The operating_systems table stores represents each type of operating system. |
124 | package_categories | 1.0a123 | | Package Categories | true | The various categories for package_definitions. |
125 | package_definition_limits | 1.0a123 | | Package Definition Limits | false | The package_definition_limits table defines the limits for each package_definition and resource combination. |
126 | package_definitions | 1.0a123 | | Package Definitions | false | The package_definitions table stores a list of supported services. |
127 | packages | 1.0a100 | | Packages | false | The packages table stores information about each package that businesses have signed up for. |
128 | payment_types | 1.0a100 | | Payment Types | true | The payment_types table stores all the acceptable payment forms |
129 | physical_servers | 1.36 | | Physical Servers | false | The physical servers consume rack space and electricity and optionally provide cluster resources. |
130 | postgres_databases | 1.0a100 | | PostgreSQL Databases | false | The postgres_databases table stores the information about each PostgreSQL database in the system. |
131 | postgres_encodings | 1.0a100 | | PostgreSQL Encodings | true | The postgres_encodings table stores the information about each PostgreSQL database encoding supported. |
132 | postgres_server_users | 1.0a100 | | PostgreSQL Server Users | false | The postgres_server_users table stores the specific attributes of postgres_users for one server. |
133 | postgres_servers | 1.0a100 | | PostgreSQL Servers | false | The postgres_servers table stores the information about each PostgreSQL instance in the system. |
134 | postgres_users | 1.0a100 | | PostgreSQL Users | false | The postgres_users table stores all the users for PostgreSQL.
Because a single person may have access to multiple PostgreSQL
servers, this table represents what is common to them across all
machines. The machine specific details are in the
postgres_server_users table. |
135 | postgres_versions | 1.0a100 | | PostgreSQL Versions | true | The <code>postgres_versions</code> is a lookup of all the available versions of PostgreSQL. |
136 | private_ftp_servers | 1.0a100 | | Private FTP Servers | false | The private_ftp_servers table contains an entry for each private FTP server hosted. |
137 | processor_types | 1.36 | | Processor Types | true | The possible types of processors for cluster QoS management. |
138 | protocols | 1.0a100 | | Protocols | true | The protocols table has an entry for each service protocol along with the default port numbers. |
139 | racks | 1.36 | | Racks | false | Each server farm may manage cluster resources on a per-rack basis. |
140 | resellers | 1.44 | | Resellers | false | A reseller may provide ticket-based support |
141 | resources | 1.0a100 | | Resources | true | The resources table stores a list of resources that may be charged |
142 | schema_columns | 1.0a100 | | Schema Columns | true | <code>schema_columns</code> stores the details about the data contained in each column. |
143 | schema_foreign_keys | 1.0a100 | | Schema Foreign Keys | true | <code>schema_foreign_keys</code> tables stores all the foreign key info for the database. |
144 | schema_tables | 1.0a100 | | Schema Tables | true | <code>schema_tables</code> stores table names, display names, and descriptions for each table. |
145 | schema_types | 1.0a100 | | Schema Types | true | <code>schema_types</code> stores names and unique numbers for each type. |
146 | sendmail_binds | 1.81.10 | | Sendmail Binds | false | The <code>sendmail_binds</code> table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be SMTP, SMTPS, or submission. |
147 | sendmail_servers | 1.81.10 | | Sendmail Servers | false | The sendmail_servers table contains a list of all the Sendmail servers. |
148 | server_farms | 1.0a100 | | Server Farms | false | The server_farms table stores the details about each unique server farm (or location) that exists. |
149 | servers | 1.0a100 | | Servers | false | The servers table keeps track of all the servers that are referenced in the database |
150 | shells | 1.0a100 | | Shells | true | The shells table stores all the shells that may be used in a linux account. |
151 | signup_request_options | 1.23 | | Sign-Up Request Options | false | The options for each specific sign-up type. |
152 | signup_requests | 1.23 | | Sign-Up Requests | false | One sign-up request for any time of service. |
153 | spam_email_messages | 1.0a100 | | Spam Email Messages | false | The spam_email_messages table stores all of the reported spam. |
154 | ssl_certificate_names | 1.81.10 | | SSL Certificate Names | false | The ssl_certificate_names contains all of the names associated with SSL certificates. |
155 | ssl_certificate_other_uses | 1.81.16 | | SSL Certificate Other Uses | false | The ssl_certificate_other_uses contains additional descriptions of how SSL certificates are used. |
156 | ssl_certificates | 1.81.10 | | SSL Certificates | false | The ssl_certificates contains all of the names and paths of managed SSL certificates. |
157 | system_email_aliases | 1.0a100 | | System Email Aliases | false | The system_email_aliases is a list of all entries that are placed in /etc/aliases
but are not part of the other tables. |
158 | technologies | 1.0a100 | | Technologies | true | The technologies table contains the list of all software packages and the classes they belong to. |
159 | technology_classes | 1.0a100 | | Technology Classes | true | The technology_classes table defines the classes that may be used in the technologies table |
160 | technology_names | 1.0a100 | | Technology Names | true | The technology_names table contains all of the unique names of software packages
that are installed in the servers. |
161 | technology_versions | 1.0a100 | | Technology Versions | true | The technology_versions table contains the list of all software packages, owners, and versions. |
162 | ticket_action_types | 1.44 | | Ticket Action Types | true | Table ticket_action_types is a lookup for all of the possible actions that may be made to a ticket |
163 | ticket_actions | 1.44 | | Ticket Actions | false | The ticket_actions table represent a complete history of the changes that have been made to a ticket.
When a ticket is initially created it has no actions. Any change from its initial state will cause
an action to be logged. |
164 | ticket_assignments | 1.44 | | Ticket Assignments | false | Tickets may be assigned to specific administrators at each reseller level. |
165 | ticket_brand_categories | 1.44 | | Ticket Brand Categories | false | Each brand may select which categories will be visible for ticket support. |
166 | ticket_categories | 1.44 | | Ticket Categories | false | Each ticket may be associated with one of these hierichical categories. |
167 | ticket_priorities | 1.0a100 | | Ticket Priorities | true | Table ticket_priorities is a lookup table for tickets |
168 | ticket_stati | 1.0a100 | | Ticket Statuses | true | Table ticket_stati is a lookup table for tickets |
169 | ticket_types | 1.0a100 | | Ticket Types | true | Table ticket_types is a lookup for tickets showing types of service requests |
170 | tickets | 1.0a100 | | Tickets | false | Table tickets contains information on service requests |
171 | time_zones | 1.2 | | Time Zones | true | The allowed time zones for a server |
172 | transaction_types | 1.0a123 | | Transaction Types | true | The transaction_types table stores all the types of transactions. |
173 | transactions | 1.0a100 | | Transactions | false | The transactions table keeps track of all transactions that have occured with the businesses |
174 | us_states | 1.0a100 | | US States | true | The us_states table contains an entry for each state in the United States. |
175 | usernames | 1.0a100 | | Usernames | false | The usernames table stores information about each username.
Every username is unique across the system, and may be used
for multiple services. Regardless of the system, the username
always belongs to one business, and preferrably one actual
person or system. |
176 | virtual_disks | 1.36 | | Virtual Disks | false | The virtual disk configurations for cluster QoS management. |
177 | virtual_servers | 1.36 | | Virtual Servers | false | A virtual server is any server that is a guest in the virtualized clustering. |
178 | WhoisHistory | 1.81.19 | | Whois History | false | Logs the whois history for each registrable domain. |
179 | WhoisHistoryAccount | 1.81.19 | | Whois History Account | false | Logs which accounts were associated with a registrable domain at the time of whois lookup. |