All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
To migrate FishEye/Crucible to an SQL Server database, install SQL Server and follow the steps below.
On this page:
Check that you are using version of SQL Server that is supported for use with FishEye. See Supported Platforms.
See the SQL Server Online resources (MSDN) for instructions on how to install and create an SQL Server database.
Please note the following FishEye/Crucible-specific information when installing and creating an SQL Server database:
Latin1_General_CS_AS collation set.In order to migrate to a different database backend, you must create a backup of SQL data, configure the database and finally import the data via a backup restoration process. This can be done from either the Crucible administration console, which streamlines the process, or via the command line tool which Crucible provides. These two methods are described below:
Before you begin:
.jar file in the classpath (by placing the .jar file in FISHEYE_INST/lib).To configure FishEye/Crucible to use SQL Server and migrate data using the Administration Console:
|
|
|
|
2. Migrating Data
|
1. Configuring the Database
|
Screenshots above: Configuring FishEye/Crucible to use SQL Server and migrating data (click to view full-size images)
To configure FishEye/Crucible to use SQL Server and migrate data using the Command Line:
sql data from the FishEye/Crucible instance. Information on how to create a backup can be found at Backing Up and Restoring FishEye Data \ Backing Up and Restoring Crucible DataRun the following command from the bin directory in FISHEYE_INST:
$ ./fisheyectl.sh restore --sql \
--file /path/to/backup.zip \
--dbtype sqlserver2008 \
--jdbcurl jdbc:jtds:sqlserver://hostname:port;databaseName=dbName; \
--username crucible \
--password password
Backing Up and Restoring FishEye Data
Backing Up and Restoring Crucible Data
Troubleshooting Databases
SQL Server Online resources (MSDN)
3 Comments
Jeremy Paskali
Jun 23, 2011You must restart the FishEye service in order for it to pickup the jtds JDBC driver .jar file in the classpath (by placing the
.jarfile inFISHEYE_INST/lib). Otherwise, you will receive error messages when testing the connection that state you are missing the database driver file.Anonymous
Dec 19, 2011I found that when connection to SQL Server 2008 I had the following error
"The database is not using Unicode. Crucible requires that the database uses a UTF8 encoding to support internalization."
This was resolved by switching to the Latin1_General_100_CS_AS collation.
Anonymous
Apr 13, 2012Thank you Mr. Anonymous. This worked for me.