On this page:
MySQL for IU Sitehosting at Indiana University is designed to provide support for IU Sitehosting users and eliminate the need for individual departments to administer MySQL database instances for their sites. IU group account owners can create MySQL accounts automatically and get nearly instant access to the central MySQL for IU Sitehosting.
MySQL for IU Sitehosting has a single instance in which account holders have root-like credentials and functionality, with access to only the databases and resources they own. Account holders can create additional users, databases (called "schemas"), and tables; they can also grant some user permissions.
Updates for Production and Test MySQL for IU Sitehosting are maintained by the Database Administration team. These servers may be unavailable during the standard maintenance window for IU Sitehosting (from 12am to 8am the second Sunday of the month), and may affect websites using the service.
For help creating an account, see Create a MySQL for IU Sitehosting account or reset a root user password.
The term "schema" has replaced "database" for MySQL documentation. Although the term "database" still works in all MySQL commands (for example,
CREATE database 'test'), the term is deprecated and may disappear from future MySQL revisions. UITS recommends adopting "schema" as quickly as possible.
In the MySQL for
IU Sitehosting single-instance environment, every user's schemas and tables are contained within a single high-performance MySQL instance. The MySQL environment does not allow any two schemas or users to share the same name, so users and schemas will have their names prepended with the group account name and an underscore (
_), as follows:
Because group account names are unique, this guarantees that content retains a unique identity within the environment. The procedures to create new objects will automatically prepend the group account name and underscore to the name.
The environment relies on a new model, the stored procedure, which is a set of commands that automates many common MySQL tasks and ensures compliance with naming conventions. To call a procedure, you must initially be connected to your MySQL account using your preferred connection method.
Procedures are formatted in the following manner (replace
procedureName with the name of the stored procedure you are invoking and include the required parameters inside the parentheses):
CALL api.procedureName(parameter01, parameter02, ...)
For a list of available procedures, use the following command:
To access the technical guide for a particular MySQL procedure, use the following command (replace
procedureName with the name of the procedure):
For more, including examples and service maintenance information, use the following command:
UITS recommends using MySQL Workbench to connect to your MySQL for IU Sitehosting account. MySQL Workbench provides a graphical environment for creating and managing connections to MySQL database servers, and features a built-in SQL Editor for executing SQL queries on those database connections.
At IU, you have the following options for using MySQL Workbench:
For more, see Use MySQL Workbench to connect to the Sitehost MySQL servers.
Since the environment is intended to provide support exclusively to IU Sitehosting, it will only accept connections to and from the IU central Sitehost and Sitehost-test servers (sitehost.iu.edu and sitehost-test.iu.edu).
Denodo is currently best suited to act as a go-between MySQL for IU Sitehosting and your external service. Connections to external sources, including Denodo, require approval from IU Sitehosting administrators and are not officially supported.
If you have questions or need help connecting to your account, email Tier 2 Web Services Support (WSS).