MySQL

MySQL is a popular enterprise-class, open-source database supported by MySQL AB. This is your best choice if you need a free, open-source database. This option scales well -- we have customers with thousands of users running off a single MySQL database.

For downloads and documentation for all platforms, see the MySQL Developer Zone web site. You'll need the MySQL Database Server component for the database itself and the MySQL Administrator component for easy, graphical server administration.

First install the Database Server component (remember that super-user username!), then install the Administrator component.

Code Collaborator needs its own database. To create one, run the Administrator application.

The Administrator application will ask for connection information. Supply the super-user username you established during database install.

To create the Code Collaborator database, first click "Catalogs" in the icon list. Then right-click in the "Schemata" area below that and select "Create New Schema". Name the new schema "collaborator".

To create the special Code Collaborator username, first click "User Administration" in the icon list. Then right-click in the "Users Accounts" area below that and select "Create New User". Name the new user "collaborator" and optionally supply a password. Then switch to the "Schema Privileges" tab, click on the "collaborator" schema, and assign all privileges by clicking the double-left-arrow button. You must click "Apply Changes" below to complete the administration.

All of these changes go into effect immediately. You do not have to restart the MySQL server for changes to take effect.

During the GUI installation screens for the Code Collaborator server, you will be prompted for the MySQL server host name, TCP/IP port, database name, user name, and password. The installer will report any connectivity errors. When you visit the web page for Code Collaborator it will detect that you have a new database and will create all tables, indexes, and views for you automatically.

1.	MySQL v4.x does not support the concept of a database VIEW object. Therefore custom reporting views are only present with v5.x servers.

Important: The MySQL native restore feature does not automatically clear the database before restoring from backup. You can use the MySQL native restore feature, but you must manually drop all tables in the database before you run the restore. By doing this, you'll ensure an exact reproduction of your backed-up database. Option two is to use the alternative method provided by Code Collaborator.