.svg)
Article Summary:
What the move from standalone SSRS to Power BI Report Server means and how to plan a controlled migration.
An SSRS change can fail far away from the installer. Reports may render while subscriptions, credentials or custom extensions break. The planning context has also changed: Microsoft is consolidating future on-premises reporting work in Power BI Report Server after SQL Server Reporting Services 2022. Existing estates need a controlled path, not an emergency upgrade.
Know the current product direction
Microsoft's Reporting Services consolidation FAQ says SQL Server 2025 on-premises reporting is consolidated under Power BI Report Server and that no new standalone SSRS release follows SSRS 2022. It also states that SSRS 2022 remains supported until January 2033.
That runway allows a planned migration. It does not remove the need to keep the current service patched, recoverable and documented.
Inventory the reporting service
List report servers, editions, versions, scale-out topology, catalogue databases, service accounts, URLs and authentication. Then inventory reports, shared data sources, schedules, subscriptions, custom assemblies, extensions and external automation. Identify business owners and critical reporting windows.
- ReportServer and ReportServerTempDB backups
- Encryption-key backup and password
- Configuration files and custom components
- Service identities and SPNs
- SMTP, file shares and data-source connectivity
Choose side-by-side where practical
Microsoft's upgrade and migration guidance distinguishes in-place upgrades from migration. A side-by-side build usually gives more room for compatibility testing and rollback. It also lets teams compare rendering and performance without taking the existing service apart.
Test beyond opening a report
Use a representative pack that covers parameter combinations, large exports, linked and drill-through reports, subscriptions, stored credentials and custom code. Validate security groups and row-level data behaviour. Record durations and output so differences can be investigated before cutover.
- Interactive and scheduled execution
- Email and file-share delivery
- PDF, Excel and CSV rendering
- Peak concurrency and long-running reports
- Monitoring, backup and restore
Cut over with rollback still available
Freeze changes, take current backups and preserve the encryption key. Migrate or restore the catalogue using the documented route, then validate service identity, URLs, data sources and subscriptions. Keep the old service isolated but recoverable until acceptance criteria and a full business cycle have passed.
Talk to a database specialist
A change to support, licensing, cloud architecture or a production database should be based on evidence from your own estate. Pro DBA can assess the current position, identify the material risks and help you plan the next step. Contact the Pro DBA team to discuss your environment.
