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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Azure SQL Database 2014 not supported JIRA Software Server

Team,

We have installed JIRA Software Server 8.12.2 and in the instance health, I'm getting an alert that, the database server version is not supported - SQL Server 2014.

We have created database from Azure SQL. Do we have any timeline from JIRA for the database upgrade?

Thanks,

Prasenna

1 answer

1 accepted

0 votes
Answer accepted

Atlassian haven't supported SQL Server 2014 for their products for quite a while.

It does, as far as I can tell, work ok for Jira 8.x, but it is unsupported, and you should upgrade it to a supported version as soon as you can.  2016 and 2017 are supported as the databases for Jira 8.12, so I would recommend upgrading to 2017 for a bit more future-proofing.

Thanks!

While installing the JIRA Software Server, I did look into the specification here - https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html

For Azure SQL, there were no details provided and now I'm getting an instance error as unsupported, for PaaS we don't have a control, why the JIRA is prompting for instance health failure?

Ok, so this is going to sound bad or grumpy, but I am trying to avoid a rambling essays:

You have found and read exactly the right documentation that you should.  And you've not just followed it by rote, you have understood it too.

So why have you installed an old and unsupported database at the back end?  Azure can provide supportable databases, is there a good reason to use a "legacy" one?

We have installed Azure SQL PaaS flavour mate and not an IaaS one. 

Yes, and you've used the wrong one.  Why did you ignore the supported versions doc you read?

@Nic Brough _Adaptavist_ : So, Azure SQL PaaS is not supported?

Yes, it is, when you use a supported database on it.

Like prasenna.kannan likes this

SQL in Azure, comes in 3 flavours ... only PaaS is in question referenced by Atlassian documentation:

- SQL Server 20XX on a VM (Infrastructure as a Service, IaaS as the OP mentioned earlier)

- SQL Managed instance, similar to above but MSFT take care of the cluster for you

- SQL Platform as a Service (PaaS) < also referred to as 'Azure SQL'.

I noticed the same issue that OP is seeing when we upgraded from DTU tier to vCore tier. There is of course no change to the version of the SQL and only the performance should be affected.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you