How to estimate upgrade time (database migration)

SonarQube Server / Community Build
,
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension):
    → 2 SonarQube Server 9.9 LTA instances, planning to move to the 2025.1 LTA
  • how is SonarQube deployed: zip, Docker, Helm
    → zip, on a Linux Server, with a Postgres database on a dedicated server;
  • what are you trying to achieve
    → upgrading from LTA to LTA
  • what have you tried so far to achieve this
    → database backup, planning;

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hi everybody,

I just want to know if there is a way to estimate (at least approximatelly) the time that the upgrade will spend on the database migration, because I have 2 instances with very large DBs (one with 230GB of data, and other with 98GB of data) and I’m having some concerns about the total period that this operation could took.

If there is something to use at least as a guide would be great; I saw some reportings/issues regarding this subject, but nothing too informative.

Thank you!

2

Hello,

The most reliable way to estimate upgrade time is to test the upgrade in a non-production environment using a recent copy of your database. This practical test will give you the clearest idea of how long the upgrade will actually take.

Keep in mind that database size alone doesn’t accurately predict upgrade duration. Factors such as the database’s contents, structure, and data types can vary significantly. For example, two databases of identical size could require different migration times—one may contain many SonarQube issues, while another could have extensive historical measure data, each affecting the migration process differently.