If you are installing SQL Server 2025 and looking for Reporting Services, you will not find it. SSRS 2022 is the last version. From SQL Server 2025, Microsoft's on-premises reporting server is Power BI Report Server. Download pages offering an SSRS 2025 are not from Microsoft.

What to install instead

Power BI Report Server runs the same paginated reports (RDL) as SSRS, plus interactive Power BI reports, on your own servers. Microsoft describes it as a superset of SSRS, and existing RDL reports are compatible.

  • A qualifying SQL Server 2025 Enterprise or Standard licence covers Power BI Report Server, installed with the same SQL Server 2025 product key.
  • On SQL Server 2022 and earlier, Power BI Report Server rights come only with Enterprise core licences on active Software Assurance, and end when it lapses.
  • Free Developer and Evaluation editions let you try it before you commit.
  • It follows Microsoft's Modern Lifecycle, with several releases a year. Plan for regular updates rather than one install every few years.

Or stay on SSRS 2022 for now

SSRS 2022 is supported until 11 January 2033. It can also keep its catalogue on a later SQL Server Database Engine, so you can move the database server to SQL Server 2025 and carry on running SSRS 2022 against it. That is a sensible holding position, but there will be no newer SSRS to move to afterwards.

Moving an SSRS server to Power BI Report Server

  • There is no in-place upgrade. Moving is a migration to a new instance.
  • Back up the encryption key first. Without it, stored credentials and connection strings cannot be restored.
  • Back up the ReportServer and ReportServerTempDB databases and restore them for the new instance.
  • Coming from SSRS 2022, you need Power BI Report Server May 2025 or later.
  • SharePoint-integrated SSRS takes more work: content is copied across with tools such as rs.exe.

Decide what moves before you move it

The technical move is the easy part. Most report servers carry years of reports nobody runs, subscriptions nobody wrote down and KPIs calculated differently in different reports. Moving all of it to a new server moves the problems with it.

  • Check which reports have actually run. The ExecutionLog3 view in the ReportServer database shows it, for as long as the server keeps history (60 days unless someone changed it).
  • List every subscription, including data-driven ones, and who receives each report.
  • Agree with owners which reports retire before the migration, not after.
  • Check the support dates for older SQL Server versions in our SSRS end-of-support guide.