If you’ve exported your database to import into a new database… once that’s done, you just need to hookup your SonarQube instance to that database and start it! No further need to import projects, etc. All the data is stored in the database.
Note that if you’re changing your DB Connection URL, it will likely invalidate your Server ID. Take a look at the documentation here: License administration
Do you have maybe some specific SQL queries which will change current URL with new ?
Second question, as we are using Developer license, is there way how to migrate configuration and projects ? For configuration ,will try to go through the sonarQube instances and will try to migrate manually config. But not sure what to do with projects, our projects/repos saved in Azure DevOps.
I am changing URL because we are migrating that instance of SonarQube to another Azure Subscription, on the end, our application it self (which was used with SonarQube) will be migrated. Probably in some point in the future Azure subscription will be deleted, and resources will be relocated to new subscription.
As this URL is public, and it is configured as Azure AppService, it is not possible to have to services with the same URL.
AppService domain is : .azurewebsites.net, in that case we will not be able to use two times same URL.
On the end, I think we will do it migration in another way.
I configured/mirrored all configuration what I found in current SonarQube, and configured a new SonarQube
I configured AzureDevOps plugin, I am able to connect project with repos from AzureDevOps but because of license, don’t work, it is asking for it.
I will request trial Developer license,
When I add trial license I can add a new step to our pipelines for new SonarQube, that mean in our steps, will be two steps for SonarQube analyse , one for current, and second for new.
and if is everything working fine, I will request a new license from sales team, anyway, our old license Is valid till end of May, and that must be requested from your Sales in any case.