Downloads (PDF, HTML & XML formats)
[FishEye Knowledge Base]
Documentation for FishEye 3.0.x. Documentation for other versions is available too.
To migrate FishEye/Crucible to a SQL Server database, install SQL Server and follow the steps below. When they are used together, FishEye and Crucible share the same external database.
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:
db_owner
role. (See SQL Server Startup Errors for details.)Latin1_General_CS_AS
collation set.Your database server should be configured to use snapshot mode for the transaction isolation level. To enable snapshot mode, run:
ALTER DATABASE crucible SET READ_COMMITTED_SNAPSHOT ON;
See this and this Microsoft MSDN articles for more information.
Note that it is preferable to run the above command after stopping FishEye/Crucible (and with no other applications connected to the SQL Server database), especially if you find that the alter
statement does not complete quickly.
In order to migrate to a different database backend, you must create a backup of your 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. The following resources may be of interest:
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:
To log in to the Admin area, you can either:
HOSTNAME
is the name of the server on which you installed Fisheye.Once logged in as an administrator you can also get to the Admin area by clicking your user menu in the FishEye/Crucible header, and choosing Administration.
Please ensure that you use a SQL Server user account to log into your database, not a Windows user account.
Screenshots: 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
3 Comments
James Slater
In "fecru-2.10.4\sql\SQLSERVER2008\schema" tables_81.sql: the following line creates a PK index (of 1128 bytes) 228 bytes larger than SQL Server's limit of 900 bytes.
create table cru_recently_visited (cru_user_name nvarchar(255) not null, cru_item_type nvarchar(80) not null, cru_entity_id nvarchar(255) not null, cru_last_viewed numeric(19,0) not null, primary key (cru_user_name, cru_item_type, cru_entity_id));
BrendanA
Thanks James for bringing this to our attention. I note that you have raised FE-4664 - Getting issue details... STATUS which describes the issue. We'll keep you posted via that issue.
Regards,
-Brendan
Charles Downs
Is there really no way to use integrated authentication? Is a SQL server account necessary?