Database procedures are compiled, stored, and managed by the DBMS Server. Database procedures can be used in conjunction with rules to enforce database integrities, or to perform frequently repeated operations. When the procedure is created, its execution plan is saved, reducing the execution overhead.

Database procedures can be created interactively or in an embedded program. A database procedure can be executed in a host language program, in terminal monitor, in another database procedure, or in a 4GL program. Database procedures can also be invoked by rules. For more information, see the chapter “Understanding Database Procedures, Sessions, and Events.”

The Object Management Extension allows data types to be created in addition to the standard SQL data types. Using the Object Management Extension, you can define operators and a function to manipulate your data types, and integrate the new data types, operators, and functions into the DBMS Server.

Ingres is largely compliant with the SQL standard and Actian has been an active member of the SQL standards process for over twenty-five years."

Information about the settings required to operate in strict compliance with ANSI/ISO Entry SQL-92, can be found in the appendix “Settings for Strict ANSI Compliance.”

OpenSQL is the subset of SQL statements that can be used to access non-Ingres databases through Enterprise Access products.

Basic Ingres installations can be administered in compliance with the C2 security standard. The following statements are of particular interest to C2 security administrators and DBAs:

For details about administering a C2 site, see the Security Guide.