Policy Code: 
Effective Date: 
Tuesday, March 9, 2004
Revision Number: 
Last Reviewed: 
Thursday, June 2, 2016
Version Control: 
This is a new standard.


Reduced total cost of ownership while increasing efficiencies in data sharing, data integrity, database support, and training.


  1. All new applications shall use databases specified in the Approved Databases list.  New databases will be presented to the Data/Information domain team for review and evaluation. The list will be updated accordingly.
  2. If data for new applications require features of an Enterprise Database, the application must utilize an Enterprise Database. Otherwise, an approved Non-Enterprise Database may be utilized.


Databases will be consistent across the Enterprise.


To all executive branch state agencies and institutions excluding the institutions under the control of the board of higher education with respect to academic and research uses of information technology.


  1. New Applications – New application software or replacement of existing application software, including all custom developed software, vendor software, and off-the-shelf software. Maintenance or enhancements to an existing application are not considered new applications.
  2. Enterprise Database definition:
    1. Ability to scale to a large number of users
    2. Provides data integrity, meaning the data in the database is consistent and accurate.
    3. Provides support for industry standards i.e. (ANSI SQL-92, ODBC, JDBC and XML).
    4. Provides for security of the data.
    5. Provides built-in audit capabilities.
    6. Provides point in time recovery.
    7. Provides backup and recovery utilities.
    8. Provides logging for backup, recovery, and auditing.
    9. Provides support large objects (BLOBS, CLOBS, etc.)
    10. Provide the basic properties of a database transaction: (ACID) Atomicity, Consistency, Isolation, and Durability
      • Atomicity – The entire sequence of actions must be either completed or aborted.  The transaction cannot be partially successful.
      • Consistency – The transaction takes the resources from one consistent state to another.
      • Isolation – A transaction’s effect is not visible to other transactions until the transaction is committed.
      • Durability – Changes made by the committed transaction are permanent and must survive system failure.
  3. Non-Enterprise Databases
    1. Agency supported.
    2. Agency specific applications that do not require the features of an Enterprise Database.
  4. Data – The raw material from which information is produced and the quality, reliability and integrity of the data must be maintained for the information to be useful.




Non-compliance with this standard shall be reported to the Office of the State Auditor.

Appendix A

Supported Database List
Database Database Type Enterprise Database
Oracle RDBMS Yes
MS Access RDBMS No

Drafted By

Data Architecture