Policy Code: 
SD004.2
Effective Date: 
Tuesday, March 9, 2004
Revision Number: 
2
Revision Date: 
Tuesday, December 19, 2017
Last Reviewed: 
Tuesday, December 8, 2020
Version Control: 
This is a new standard.

Purpose

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

Standard

  1. All new applications shall use databases specified in the “Supported Databases” list.  New databases will be presented to the Data Architecture 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.

Policy

Databases will be consistent across the Enterprise.

Applicability

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.

Definition

  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:
  3. Ability to scale to a large number of users
  4. Provides data integrity, meaning the data in the database is consistent and accurate.
  5. Provides support for industry standards (i.e. ANSI SQL-2011, ODBC, JDBC and XML).
  6. Provides for security of the data.
  7. Provides built-in audit capabilities.
  8. Provides point in time recovery.
  9. Provides backup and recovery utilities.
  10. Provides logging for backup, recovery, and auditing.
  11. Provides support large objects (BLOBS, CLOBS, etc.)
  12. 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.

Guidance

None

Non-Compliance

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

Appendix A - Supported Databases

Database

Oracle                      

MS SQL Server      

MySQL

Appendix B - Legacy/Deprecated Databases

Database

IBM DB2

ADABAS

 

Drafted By

Data Architecture