Add Custom Tables to a Custom Schema

•Definitions – "schema" versus the "EQuIS Schema"

Per the EQuIS Database Modification Compliance Requirements, database administrators can add tables to their EQuIS databases, but only within a custom schema (defined below).

EarthSoft also recommends that additional custom fields be added to custom tables, rather than standard tables.

Definitions – "schema" versus the "EQuIS Schema"

In this page, schema refers to the SQL Server definition of a collection that can store database objects (such as tables, views, stored procedures, and functions) and where collective permissions can be assigned.

Compare this definition to the "EQuIS Schema", referring to the entire structure of a standard EQuIS database. Standard schemas contained within the EQuIS Schema include the following:

•dbo (default for tables and views, deprecated stored procedures and functions)

•equis (for stored procedures and functions)

•v54 (for older EQuIS database reports)

The EQuIS Schema files for each module include code that updates these schema, for example, schema.Enterprise.xme in the EQuIS Professional installation's db folder. EarthSoft does not recommend modifying the standard schemas (dbo, equis, and v54) outside the terms of the EQuIS Database Modification Compliance Requirements. Such changes may affect database behavior and result in limited support.

A custom schema allows greater permissions for object creation without losing control over the standard dbo schema. It also lowers the risk of errors or inadvertent changes to custom tables when updating the EQuIS database to a new build. For more information, see Microsoft documentation page Create a Database Schema.