Forum Discussion
Prevent loading times irrelevant Excel tabs
Hi PVO
As tested, when i connect to a XLSB file with Power BI, it would consume more time than XLSX file.
I would suggest you to save the XLSB file as an XLSX file instead.
the way Power Query connects to XLSB files and XLSX files is very different.
- The XLSX file import uses the OpenXML SDK to get into the actual data
- The XLSB file import (and XLS and some other non XML formats) uses the ACE OLEDB Driver (the one used to import Access data).
The bottom line is the OpenXML import approach is far more efficient than the one that uses the ACE OLEDB driver. While this may not be an issue with smaller XLSB files, it seems that it can be an issue for larger files.
Best Regards
MaggieCommunity Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi PVO
As tested, when i connect to a XLSB file with Power BI, it would consume more time than XLSX file.
I would suggest you to save the XLSB file as an XLSX file instead.
the way Power Query connects to XLSB files and XLSX files is very different.
- The XLSX file import uses the OpenXML SDK to get into the actual data
- The XLSB file import (and XLS and some other non XML formats) uses the ACE OLEDB Driver (the one used to import Access data).
The bottom line is the OpenXML import approach is far more efficient than the one that uses the ACE OLEDB driver. While this may not be an issue with smaller XLSB files, it seems that it can be an issue for larger files.
Best Regards
Maggie
Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
v-juanli-msft Wow Maggie!
Thanks a lot. This was a very, very significant quick fix.
I made a fast comparison of loading times.
| extension | connection + preview window | load sheet |
| xlsb | 3 seconds | 6 seconds |
| xlsx | 180 seconds | 405 seconds |
| xlk | 180 seconds | 450 seconds |