Lost data after database migration - Jira Service Desk

[Michael Johnson]

Background:

The original SQLServer database was setup with a particular collation.  this worked just fine until we tried to do an upgrade to 4.6.1 and we received and error that SQL_Latin1_General_CP1_CI_AS is not supported and that we need to change our collation to SQL_Latin1_General_CP1_CS_AS.  We created a new database with the new collation.  We exported the data from the old database and imported it into the new database.

Problem:

The data is not there - meaning, the data seems to be correctly imported into the database, but I no longer see my projects or my data.  I believe I have close to 1.5 years amount of work int to the Jira Service Desk instance.  

I tried to migrate back (point to the old database), but I still do not see my data.  I see some of the theme customizations that I did (I assume these are part of some CSS file that is stored locally).  

Possible Issues:

The person that did my migration changed the system to use https vs. http.  I get a message when I log in that:  "Jira's base URL is set to:  http://xxx.xxx.xxx:8080, but you are accessing Jira from https://xxx.xxx.xxx:8443.  Update Jira's base URL."

Questions:

1.  What did we do wrong?

2.  Can we retrieve the data or am I stuck trying to recreate what I have already done?

3.  Is this problem due to the database or the URL?

[Brant Schroeder]

Michael,

  Do you have backups of everything?  You might want to start over or perform the upgrade again.   Couple of questions.

1. Have you updated the base URL yet?  (I don't think this has anything to do with your issue but you could do it to get rid of the notification.) https://confluence.atlassian.com/adminjiraserver/configuring-the-base-url-938847830.html
2. When you say you are not seeing anything does that mean that all your projects, issues, users, etc are missing?
3. How was the upgrade performed.  Did you make the database changes and then perform the upgrade with the application pointing at the new DB?  Did you perform the upgrade them make the DB change?  
4. Is the new DB on the same SQL server instance?  Is the application connecting to the new DB?  Are you seeing any errors in the logs?
5. If you look in the DB is all the information there?