Information Technology Services

University Databases

Databases

Management Information Systems (MIS) supports central databases built with Oracle Corporation's Relational Database Management System. The Database Administrator or assistant will create user accounts in central administrative databases. All database user accounts will be assigned a password at the time they are created. User accounts in production databases will be assigned to a security class when the account is created.

• Banner Database Instances
  • Production Database
  • Validation Databases
  • Development Database
  • Seed Database
• Other Database Instances
  • Continual Learning Database
  • Institutional Research Database
  • Resource 25 Database
  • Resource 25 Development Database
  • Multi-MIMSY Database
  • Multi-MIMSY Development Database

Banner Database Instances

This section describes the central database instances maintained by MIS in support of the Banner Student, Accounts Receivable, and Financial Aid system for The University of North Carolina at Greensboro (UNCG). It includes a description of the purpose, access control, processing requirements, and ownership for each instance.

Production Database

• Name: BANPRD
• Purpose:
  • Store UNCG data for access by authorized UNCG users to support administrative functions of the University. Many users across the University share this data. The Banner Project Team resolves any conflicts concerning the format or meaning of the data.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control under Oracle Roles and Banner Classes established by the Security Committee.
  • Referential integrity is strictly enforced.
  • Application programming staff has read-only access as required to maintain application systems.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
  • New programs loaded by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
  • No test data shall be entered into this database.
• Location:
  • Resides on CERES running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro.

Validation Databases

• Name: UGVAL1
• Purpose:
  • Through June 1998 — Used to test data entry and procedures for offices not yet in production on BANPRD. Integrity of database may be suspect. Rollover of data from UGVAL1 to BANPRD performed by Database Administrator under guidance and control of Project Team and Project Manager. Populated with production data on an as needed basis.
  • After June 1998 — Loaded with known data for testing by University departments of changes and enhancements to system prior to implementation in production database.  Implementation in production performed by Database Administrator under coordination of the Banner Project Team. Populated with production data on the first Tuesday of each month and at other times as needed and coordinated with the Project Team.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control under Oracle Roles and Banner Classes established by the Security Committee.
  • Referential integrity is enforced.
  • Application programming staff has read-only access.
  • Data imports performed by Data Base Administrator.
  • Database repairs performed by Data Base Administrator or assistant.
  • New programs loaded by Data Base Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
• Location:
  • Resides on GRACE running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Banner Project Team.

• Name: UGVAL2
• Purpose:
  • Used to install and populate new modules when acquired and major new enhancements prior to implementation in the production database.  Implementation in production performed by Data Base Administrator under coordination of Banner Project Team. Populated with production data as needed.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control under Oracle Roles and Banner Classes established by the Security Committee.
  • Referential integrity is enforced.
  • Application programming staff has read-only access.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
  • New programs loaded by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
• Location:
  • Resides on AEGIS running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Banner Project Team.

Development Database

• Name: UGDEV1
• Purpose:
  • Used only by MIS for system modification and new development. May be used to test new Banner upgrades with known database load from BANPRD.
  • Data may be deleted and/or modified at any time. No referential integrity enforced.
  • No data rollover into UGVAL1 or BANPRD, but rollover may occur in the other direction. Developers may maintain private reloads for testing purposes. No coordination required outside MIS.
• Access:
  • All data entered by authorized UNCG programmers only.
  • Security and access under control of MIS.
  • New programs added by UNCG programmers.
• Requirements:
  • All data entered according to approved data entry standards.
• Location:
  • Resides on AEGIS running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Management Information Systems.

Seed Database

• Name: UGSED1
• Purpose:
  • Used only by Data Base Administrator for test load of new SCT, Oracle, or Digital Equipment software.
  • Data may be deleted and/or modified at any time. No referential integrity enforced.
  • No data rollover into UGVAL1 or BANPRD. Data Base Administrator may maintain private reloads for testing purposes. No coordination required outside MIS.
• Access:
  • All data entered by Database Administrator only.
  • Security and access control to Database Administrator only.
  • Database repair via reload.
• Location:
  • Resides on AEGIS running under VMS.
• Ownership:
  • University of North Carolina at Greensboro MIS Database Administrator.
    

Other Database Instances

This section describes the central database instances supported by MIS for departments of UNCG. It includes a description of the purpose, access control, processing requirements, and ownership for each instance.

Continual Learning Database

• Name: UGTST1
• Purpose:
  • Used in support of the processing requirements of the Division of Continual Learning.
• Access:
  • All data entered by authorized Continual Learning users only.
  • Strict security control under Oracle Roles and Banner Classes established by the Division of Continual Learning.
  • Referential integrity is strictly enforced.
• Requirements:
  • All data entered according to approved data entry standards.
  • No test data shall be entered into this database.
• Location:
  • Resides on GRACE running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro.

Institutional Research Database

• Name: UGTST1
• Purpose:
  • Provide a data warehouse for Institutional Research processing and reporting requirements.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control under Oracle Roles.
• Requirements:
  • All data entered according to approved data entry standards.
  • No test data shall be entered into this database.
• Location:
  • Resides on GRACE running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Office of Institutional Research.

Resource 25 Database

• Name: RES025
• Purpose:
  • Support data storage and processing for the Resource 25/Schedule 25 system as implemented by the University Registrar.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control utilizing Oracle Roles established by the software vendor.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
  • No test data shall be entered into this database.
• Location:
  • Resides on GRACE running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro University Registrar.

Resource 25 Development Database

• Name: DEVRES
• Purpose:
  • Provide development/test database for the Resource 25/Schedule 25 system as implemented by the University Registrar. Loaded with know data for testing by University Registrar personnel of changes and enhancements to system prior to implementation in the production database. Implementation in production performed by Database Administrator.  Populated with production data as needed and coordinated with University Registrar personnel.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control utilizing Oracle Roles established by the software vendor.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
• Location:
  • Resides on AEGIS running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro University Registrar.

Multi-MIMSY Database

• Name: MMIMSY
• Purpose:
  • Support data storage and processing for the Weatherspoon Art Gallery's art inventory.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control utilizing Oracle Roles established by the software vendor.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
  • No test data shall be entered into this database.
• Location:
  • Resides on GRACE running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Weatherspoon Art Gallery.

Multi-MIMSY Development Database

• Name: DEVMIM
• Purpose:
  • Provide development/test database for the Weatherspoon Art Gallery's Art Inventory system. Loaded with know data for testing by Weatherspoon personnel of changes and enhancements to system prior to implementation in the production database. Implementation in production performed by Database Administrator. Populated with production data as needed and coordinated with Weatherspoon personnel.
• Access:
  • All data entered by authorized UNCG users only.
  • Strict security control utilizing Oracle Roles established by the software vendor.
  • Data imports performed by Database Administrator.
  • Database repairs performed by Database Administrator or assistant.
• Requirements:
  • All data entered according to approved data entry standards.
• Location:
  • Resides on AEGIS running under VMS.
• Ownership:
  • The University of North Carolina at Greensboro Weatherspoon Art Gallery.