Standard procedure is to explort the database using the XML backup, then import it into an empty Jira pointed at the new database.
(Part of me is curious to know why you're downgrading - there's only one time I'd recommend a move to MS-SQL, just wondering if you fall into that situation, because if you don't, you probably shouldn't be doing this move)
We are currently using JIRA version 4.1.2 with mysql version 5.0.83-community-nt and planning to move JIRA database to mssql 2012. Is there a step by step procedure on how to proceed with this upgrade? We are not trying to do a downgrade. We are upgrading JIRA at same time.
What is the one time move that you recomment from MS-SQL?
A move to MS-SQL is always a downgrade, it's simply not as good as Post, My or Oracle. The only time I'd recommend it is when you really don't have any expertise with the other three available. You should always go with what you can support best.
For the upgrade, 4.2 to 6.3 is a valid step, but as always, you will need to test it for yourself. If your Jira is smallish, has few plugins (or at least the ones you have are good with upgrades) and hasn't been customised, you'll probably be fine.
But test it. And read the release notes for 4.3, 4.4, 5.0, etc
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs