Skip to main content

Dataset backup and restore performance just got a lot better

In August 2021, we announced general availability (GA) of backup and restore for large datasets. Not content, we looked for additional ways to improve this important feature. One area stood out: performance. After all, the faster you can backup and restore your datasets in Power BI, the more you can minimize downtime in critical situations and uphold your service level agreements (SLAs). Of course, better performance also helps with backup and restore based migrations of Azure Analysis Services (AAS) datasets to Power BI.

Today, we’re happy to announce significant performance improvements to backup and restore operations. Our benchmark tests with 1GB, 5GB, and 10GB datasets show backups can now be completed up to 22 times faster than before, and the time required for restore operations can also be reduced by more than 30%.

With the goal of improving the speed of backup and restore for large datasets, we evaluated several critical areas in the Analysis Services engine. The Analysis Services engine is the key component in Power BI that loads and processes datasets and answers analytical queries. It’s also the key component in backup and restore operations. Our evaluation showed that datasets over 1GB offered significant improvement potential. This potential was even greater with increasing dataset sizes. You can see this in the chart below showing the backup duration in seconds (DurationSec) by dataset size (DB Size).

The backup process in-particular exhibited a non-linear duration as the dataset size grew. At a dataset size of 30GB, we finally reached a threshold that compelled us to prioritize making changes to the backup logic.

Restore operations performance also improved. As shown below, our evaluations showed a 33% performance improvement, which is a substantial gain when you need to urgently recover a database.

These backup and restore performance improvements are now available in Power BI without requiring any configuration changes or optimizations to your datasets. If you notice that your backups complete in a fraction of the time it took previously, rest assured your backups did complete successfully. They just completed faster.

And that’s it for this quick announcement of these exciting backup and restore performance improvements in Power BI. Be sure to check out Backup and restore datasets with Power BI Premium to learn more about how to use dataset backup and restore and multi-geo considerations.

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular posts from this blog

SSRS INTERVIEW QUESTIONS

Q: What is SSRS? Ø   SSRS or SQL Server Reporting Service is a server-based report generation software systems from Microsoft and is part of Microsoft BI. Ø   It is used for preparing and delivering interactive and variety of reports. Ø   It is administered through an web based interface. Ø   Reporting services utilizes a web service interface for supporting and developing of customized reporting applications. Ø   SSRS lets you create very rich reports (Tabular/Graphical/Interactive) from various datasources with rich data visualization (Charts, Maps, sparklines) Ø   SSRS allows are reports to be exported in various formats (Excel, PDF, word etc) Q: Explain SSRS Architecture? Reporting services architecture comprises of integrated components. It is a multi-tiered, included with application, server and data layers. This architecture is scalable and modular. A single installation can be used across multiple computers. It includes the fo...

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got...

Failed to execute the package or element. Build errors were encountered

Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package