No documentation on SQL DB minimum requirements?

SonarQube Server / Community Build
1

I’m working with our DevOps team to set up SonarQube Community 2026.1 on our GKE cluster for testing.

The sonar DB Installation documentation says that we can set up an external Postgres DB, but there’s no information on what CPU/RAM/Storage we should select for a small vs large DB. There is a large cost difference between small vs large DB, so this is important for new users installing SonarQube. Can the Sonar team please update that DB page to include some “minimum requirement” guidelines for small vs large DB installations to base our sizing off of?

Related links:

2

Hi,

It depends entirely on what you anticipate having under analysis, but the docs shoudl help.

 
Ann

3

Thanks for sharing the link. I see it says:

  • VM Configuration:
    • 2vCPU
    • 8 GB RAM
    • 30 GB table space
  • AWS RDS:

    • db.t3.large

    • 30 GB table space

  • Azure SQL:

    • B2ms

    • 30 GB table space

  • Google Cloud SQL:

    • 2 vCPU

    • 8 GB memory

    • 30 GB table space

Can we add a similar “Reference Architecture” page into the “SonarQube Community Build” docs too?

5

Hi,

The presumption is that if your instance is large enough / critical enough that you’re worried about this, then you’re in a commercial edition. :sweat_smile:

More seriously, I’ve flagged this for the docs team.

 
Ann

6

Thanks. It’s just the Community docs have no info at all right now, so I don’t even know whether I should allocate 1GB or 100 to get a bare minimum install going for Community. Looking forward to the updates.