Forum Discussion
Helper IVPower BI Report Server migration to new servers
We have three Power BI Report Server environments with each of these enviornments having a development, unit acceptance testing, and production setups. These environments were set up 8 years ago and are running on Windows Server 2016 (operating system) and SQL Server 2016 (for the report server databases).
We are setting up new servers with Power BI Report Server to run on Windows Server 2025 and the Power BI Report Server database to run on SQL Server 2025 on Windows Server 2025.
I have a couple of questions. The first and most basic is bringing the existing folders and reports to the new server. When cloning the original Power BI Report Server database (on SQL Sever 2016) to the new SQL Server 2025 is all that needs to be done? Do all the folders, reports, and security (on folders and reports) come over as well? I am just verifying.
The second question is that we are thinking of consolidating all three environments into one consisting of DEV, UAT, and PROD. How would this be done. I see that one environment can be migrated over with the original database cloned to the new SQL Server 2025 instance (for example when we are doing DEV). How would the other 2 DEV environments be brought over to the new DEV environment. They each have their own database so the cannot be restored over the new database which has the PBIRS database from the first environment. For the other 2 DEV environments would we have to create the folder structures on the new DEV PBIRS and manually copy all the reports to it? Would we then have to duplicate the manually duplicate the permissions? We are looking for advice on whether to pursue one consolidated environment or build three new environments (each consisting of DEV, UAT, and PROD).
Hi Lorenz33 ,
Thanks for sharing and Yes, your understanding is correct.
PBIRS is a stateless service, meaning all content is stored in the ReportServer databases. When you Backup and restore
- ReportServer
- ReportServerTempDBR
Restore the encryption key
Configure the new PBIRS instance to point to the restored databaseYou will automatically bring over-
-Folder structure
-Reports (RDL + PBIX stored in PBIRS)
-Data sources
-Subscriptions
-Security (folder & item-level permissions)This is the standard Microsoft-supported migration approach-https://learn.microsoft.com/en-us/power-bi/report-server/migrate-report-server
2. Consolidating 3 Env into One-
Direct Database Merge is NOT Supported
Each PBIRS environment has its own ReportServer database, There is no supported way to merge multiple, ReportServer databases ,IDs, metadata, and catalog structures will conflict. rathere then that you can keep seperate env -- Migrate each environment independently
- Maintain DEV / UAT / PROD separation
Alternatively Instead of merging everything technically Consider logical consolidation-
- Single PBIRS instance
- Separate folders for each environment
- /DEV_Env1 ,/DEV_Env2, /DEV_Env3
OR- Separate PBIRS instances:
- PBIRS-DEV
- PBIRS-UAT
- PBIRS-PROD
This keeps isolation while reducing infrastructure complexity.Always use a side-by-side migration approach (old system stays live until validation is complete)PBIRS Migration Best Practices -
https://community.fabric.microsoft.com/t5/Report-Server/Migration-of-Power-BI-Report-Server-On-Premises-from-older/m-p/4729648- Use DB restore approach for each individual environment
Avoid trying to merge databases
If consolidation is required, use content migration and logical separation.
For simplicity and governance, maintaining separate environments is often the safest choice.
Hope this helps clarify both the migration and consolidation paths.If This reply helps you finnd answer please mark it as asolution.Thank youSunita
1 Reply
- trivedisunita
Continued Contributor
Hi Lorenz33 ,
Thanks for sharing and Yes, your understanding is correct.
PBIRS is a stateless service, meaning all content is stored in the ReportServer databases. When you Backup and restore
- ReportServer
- ReportServerTempDBR
Restore the encryption key
Configure the new PBIRS instance to point to the restored databaseYou will automatically bring over-
-Folder structure
-Reports (RDL + PBIX stored in PBIRS)
-Data sources
-Subscriptions
-Security (folder & item-level permissions)This is the standard Microsoft-supported migration approach-https://learn.microsoft.com/en-us/power-bi/report-server/migrate-report-server
2. Consolidating 3 Env into One-
Direct Database Merge is NOT Supported
Each PBIRS environment has its own ReportServer database, There is no supported way to merge multiple, ReportServer databases ,IDs, metadata, and catalog structures will conflict. rathere then that you can keep seperate env -- Migrate each environment independently
- Maintain DEV / UAT / PROD separation
Alternatively Instead of merging everything technically Consider logical consolidation-
- Single PBIRS instance
- Separate folders for each environment
- /DEV_Env1 ,/DEV_Env2, /DEV_Env3
OR- Separate PBIRS instances:
- PBIRS-DEV
- PBIRS-UAT
- PBIRS-PROD
This keeps isolation while reducing infrastructure complexity.Always use a side-by-side migration approach (old system stays live until validation is complete)PBIRS Migration Best Practices -
https://community.fabric.microsoft.com/t5/Report-Server/Migration-of-Power-BI-Report-Server-On-Premises-from-older/m-p/4729648- Use DB restore approach for each individual environment
Avoid trying to merge databases
If consolidation is required, use content migration and logical separation.
For simplicity and governance, maintaining separate environments is often the safest choice.
Hope this helps clarify both the migration and consolidation paths.If This reply helps you finnd answer please mark it as asolution.Thank youSunita