We are currently at 9.9.0 SQ enterprise version, which is deployed via helm on AKS cluster and using azure postgre SQL flexible server for data storage. We are planning to move SQ instance to new cluster. Now that latest version is 10.3.0, I have deployed new version on target cluster. I was hoping for a project export/import. but since it requires same version I can’t use that feature. Any suggestion here?
Also, we have about 140 projects. export/import is lots of manual work. anyone can suggest better options? we want to keep data from previous analysis.
What if we can just simply connect new SQ instance with same old DB? Is this something can be done?
Thanks Ann. I would definitely try this. what are you thoughts on connecting multiple sonarqube instance to same azure postgreSQL DB? Is it doable? I am asking as we only have production environment and can’t perform much testing for this.
I have copied DB to new server and successfully connected stage instance to that. But problem I am facing now is copied database had sonarqube URL value of old instance. Because that is also copied in new server, now new instance is automatically updated and redirected to old instance. Would you know which table this setting is saved in or where or how to update it? I can’t do it via UI as UI is redirected to old instance and which will make change in old instance rather new.
I don’t fully understand what’s happening with the redirect, but I also don’t know what table this is in. As a general rule, we say the DB should be treated like a black box and you should keep your hands out of it. You’ll need to sort out the redirct problem, I think. Once you do, you can change the URL on the Administration page. Just scroll down.
thanks for the quick reply. After I connected sonarqube instance to DB, it was saying DB upgrade required. so as per one of forum advise, I went to SQURL/setup page and started upgrade. It restarted pod and I saw in log that server URL and server ID might have changed. So now when I go to new URL, it automatically redirect to old URL and because OLD URL is pointing to old working instance, it is connecting us to old system.
As you said, changing URL in administration page would change relevant settings in DB automatically?