Hi,
As an organisation, we're currently looking at updating our core business application which will in turn provide opportunities to upgrade our reporting infrastructure.
Presently, we've rolled out PowerBI and have made several reports and dashboards available to end users. We still however have our legacy Reporting Server site which houses 2-300+ .rdl files built against 2008 R2.
When our business application is upgraded, we will be moving our reporting from an on-premise SQL Server hosted in Azure to an Azure Data Factory (PaaS) to service our reporting. In the interim, we will still need access to the legacy reports whilst we decide what to migrate to our PowerBI model and what can be discarded.
Realistically, how feasible would it be to migrate our reports from Report Server to the PBI Service?
My current thinking is that we would do the below in PowerShell but I'm not 100% all of it would be feasible; has anyone else got a similar experience or any advice on this?
- Loop each .rdl and update its XML to include new definitions as part of PBI Paginated.
- I've done the reverse but as a one off job i.e. removing the elements that aren't recognised by 2008 and renaming the report definition.
- Update Connection String to point at our new environment
- Save a copy of each report (so not to break the current ones)
- Upload each file to PowerBI Service
Unfortunately, the business need is that we keep these older reports which will naturally be less efficient but the plan will be to whittle away any that aren't relevant pre-migration. I want to have this process as automated as possible, namely in that I don't want to be manually dragging 2-300 files across myself!
Also, if we suddenly dump these files to the PBI server, will this also have an impact on our premium capacity usage? My gut feeling is that it will and may mean we need to upgrade (currently on P1).
Any thoughts? Any similar experiences?