Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

The database is not using Unicode Issue

vijay garg
vijay garg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
December 5, 2012

Hello,

I am trying to configure FishEye/Cricible to use SQL Server 2008 and getting following error:

The database is not using Unicode. FishEye and Crucible require that the database uses a UTF8 encoding to support internalization.

I can not make changes in DB for this. Is there a way so I can run FishEye/Crucible to be compatible with SQL Server 2008 character encoding?

Thanks

Answer
Watch
Like Be the first to like this
441 views

1 answer

0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
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.
Get recognized
December 5, 2012

Not without rewriting parts of the application. This isn't gospel, it's based on one of the developers here spending a day looking into it and coming back with a strong recommendation that we change the database (we took the opportunity to drop MS-SQL and move to PostGreSQL). I'd raise it with Atlassian directly for an authoritative answer, but I'd highly recommend revisiting the "cannot change database" while you wait.

Reply

Suggest an answer

Log in or Sign up to answer
Fisheye
Fisheye/Crucible
TAGS
AUG Leaders

Atlassian Community Events

    See all events