Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Change SQL-server compability mode


We have a SQL server 2019 and for our bitbucket installation we have enabled compability mode on the server to SQL server 2012 (110). 

We were going to upgrade our bitbucket to the latest version (v7.11.1 installed today), but the latest version didn't support SQL server 2012, so we couldn't go through with the upgrade. 
So our plan is to change compability mode to 2019, which our version of bitbucket support, first and then upgrade to the latest version. 

Do you know if there's any risk involved in changing the compability mode on the SQL-server? Can it harm bitbucket in any way or is it safe to change the compabiltity mode before the upgrade? 

Thank you

0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events