Can we define collation type at database, rather than server, for FishEye

Tim Davis February 2, 2014

We're just finishing an evaluation of FishEye (really good product) and am looking at agreeing the final resting place for the database, aiming for MS Sql Server.

Our SQL Servers normally use "Latin1_General_CI_AS" collation, whereas FishEye needs "Latin1_General_CS_AS".

Are we best creating a new server instance for "Latin1_General_CI_AS", or are we able to get away with creating a database with "Latin1_General_CI_AS" collation only?

Probably the first I suspect ...

1 answer

1 accepted

1 vote
Answer accepted
AafrinA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2014

Hi Tim,

For your reference, the server requirement for the Fisheye and MSSQL are as mentioned here. As mentioned in the requirement, Your database server must be configured to use the Latin1_General_CS_AS collation set. The following collation type can be set at the database level instead of setting to the whole server and interrupting other database instances within your MSSQL Server.

Tim Davis February 12, 2014

Thankyou. We've concluded that we'll create a new SQL Server instance with the correct collation type, rather than define at the database. Just to ensure we do not hit any problems in future.

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events