SonarQube Enterprise comes with 2 additional licenses

which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension): 8.2
what are you trying to achieve: Once we buy Enterprise License for SonarQube, We get 2 additional license copies for staging/test and 1 Production.
Is there some caching enabled between those licenses? do I need to analyse same projects with those 2 additional licenses? Or can I analyse different projects?
what have you tried so far to achieve this: analyzing still


Those additional licenses are for staging environments. Ideally you’re going to use them to test upgrades, changes to your rule profiles &etc. So yes, you’ll probably end up analyzing the same projects that you do on the production instance.



Thanks for the update @ganncamp, We are estimating on infra requirements for SonarQube.

I have couple of questions.

  1. Do I need to install each of the license on different servers? Or is it possible to install it on same server?
  2. If we need to install it on different server, Is there some communication/synchronization happens between those instances?
    is it required them to be on same network?

Could you please guide me through these steps, I did not find any documents on it.


Hi Abhishek,

It’s possible, but maybe not desirable. Why? One of the features that Enterprise Edition comes with is the ability to run multiple, concurrent compute engine threads. These are the threads that do the server-side analysis report processing. If you have an active instance, you might want to tune that to multiple threads (the default is 1) to clear the analysis report processing queue faster, so that Project A isn’t stuck waiting for Project C to finish. But when you turn that on, you’ll need to carefully manage the resources you give the instance (there’s a docs page that touches on this). And that’s why you probably want your production SonarQube instance to run alone on its own box. That said, I don’t know of a reason off-hand you couldn’t run the other two instances together on the same box. You’d just need to be careful to tune the ports of each instance so they didn’t clash.

No, and no. :smiley:


1 Like

Hi Abhishek,

  1. you’re not obliged to, but using the same machine for more than one instance doesn’t make
    sense with regard to performance, space management, backup, patches …

    It’s similar to the build machine, take the best you can get.
    A test instance should use exactly the same setting as the production instance.
    I guess you won’t run a production instance parallel to other tools, sharing memory, space !?

    We run our instances on single VMs.
    First testing instance is for internal use only, implementing + testing new rules / plugins, new
    Sonarqube versions.
    Second instance is open for others too and part of the test pipeline toolchain.
    Final tests before upgrading use a copy of the productive Sonarqube database.

  2. no, every instance has its own database and is independant of other instances.
    Sonarqube is a standard stage of any build pipeline, you need to make sure the communication
    between Sonarqube <-> Buildserver, e.g. Jenkins works.
    We do run one central Sonarqube instance with different networks, means proxies and firewalls
    involved. The setup is more challenging.



That helps!! Thanks @ganncamp & @Rebse

1 Like