This page last changed on Feb 07, 2011 by sruiz.

This page contains instructions for migrating from your default embedded FishEye database to an external database. You may want to migrate to an external database for the following reasons:

  • Improved Protection Against Data Loss: The FishEye built-in database, which runs HSQLDB, is susceptible to data loss during system crashes. External databases are generally more resistant to data loss during a system crash. As of FishEye 2.4, HSQLDB is not supported in production environments and should only be used for evaluation purposes.
  • Performance & Scalability: If you have a large number of users on your FishEye instance, running the database on the same server as FishEye may slow it down. When using the embedded database, the database will always be hosted and run on the same server as FishEye.
  • Data Stored in the FishEye Database: The FishEye database stores information besides the cache for repository scans. Specifically, user data and user preferences information.

Overview

You can use a number of alternatives to the built-in HSQLDB database for storing FishEye and Crucible's relational data. The supported alternative databases are listed on the Supported Platforms page. Please note, that only the database versions listed on that page are supported.

The pages linked below outline the steps required to switch to an external database:

Support for other Databases

If you are looking for support for Microsoft SQL Server, please vote for the issue below:

If you are using another database product that you would like to see supported, please create a JIRA issue for it under the Crucible project.


Document generated by Confluence on Apr 03, 2011 23:09