Database Schema Request Form - UW–⁠Madison Information Technology

Please select the enterprise database type that you are requesting:*

Oracle

MySQL

(While a shared MySQL hosting solution is not yet available, we do provide MySQL administration or consulting support, and complete support for individually hosted instances. Please provide your contact information below so we can discuss your MySQL needs.)

Provide a detailed description of your database:

Email*

Administrative Contact Information

Name*

Enter your first and last name

NetID*

Enter your NetID

Email*

Enter your wisc.edu email address

Telephone*

Enter your area code and telephone number

Technical Contact Information

Who will be the technical contact for this database?*

If you will be the technical contact, click "I am the technical contact for this database." Otherwise, click "Another person is the technical contact for this database."

I am the technical contact for this database.

Another person is the technical contact for this database.

Technical Contact Name*

Enter the technical contact's name

Technical Contact NetID*

Enter the technical contacts NetID

Technical Contact Email*

Enter the technical contact's wisc.edu email address

Technical Contact Telephone*

Enter the technical contact's area code and phone number

Customer Contact Information

Who will be the customer contact for this database?

If you will be the customer contact, click "I am the customer contact for this database." Otherwise, click "Another person is the customer contact for this database."

I am the customer contact for the database.

Another person is the customer contact for this database.

Customer Contact Name*

Enter the customer contact's name

Customer Contact NetID*

Enter the customer contact's NetID

Customer Contact Email*

Enter the customer contact's wisc.edu email address

Customer Contact Telephone*

Enter the customer contact's area code and phone number

Billing Information

The rate for database schemas is based on the size of the schema. The schema charge is $16 per GB per month which includes the routine database and environment support (e.g., patching.)If a schema is 0GB to 1GB in size the charge is $16, if a schema is >1GB to 2GB the charge is $32, etc. Example: The total cost of schema X at 1.5GB would cost $32/month for a total of $384/year. Note that application-specific DBA support, such as a user request to restore a particular schema, is not included in these charges.

Database size	Price*
0-1GB	$8 / month
1-5GB	$16 / GB / month
More than 5GB	$14.5 / GB / month

Type of Monthly Billing*

Select which type of monthly billing to use, CBS number or DoIT number

DoIT CBS Project Number

DoIT Number

DoIT CBS Project Number*

8 digit number, ex 10001234. More information at https://doitnet.doit.wisc.edu/CBS/ViewDetail.asp?id=101

CBS Task Number*

DoIT Number*

Enter your DoIT number

Database Account Information

Preferred Schema Name*

3 character personal schema requests are reserved for an individual account. Such accounts may not be used for production applications.

Application Name*

Enter the aplication name

Application Location (Where does the application live?)*

The application using Oracle must be hosted on the DoIT Platform.

Approximate Initial Data Size (GB):*

Requests to host small amounts of data may result in your account being created in a shared database. The DB hosting team will work with you to make the best choice.

Approximate Data Size After 1 Year (GB)*

Enter the approximate data size after one year, in gigabytes.

Environment*

Is the schema to be created in the test or production environment or both?

Test

Production

Both

Security Information

Restricted Data

Review guidelines for Handling sensitive university data.

I am storing restricted data within this database account.

Sensitive information (passwords, restricted data etc.) stored within the database is encrypted.

I am storing protected health information (as described in the about url).

Comment

Is there anything else we should know?

This field is for validation purposes and should be left unchanged.