Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreShape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.
Ive connected up to the Adventureworks DW to give a demo pf Power BI. The pbix file i 317097 kb
The Fact table contains 11,669,638 rows. Is there anything I can do to speed things up. I have to wait ages moving from the dashboard to the report. And I wont be able to publish in the demo because it takes way too long
Hi @DebbieE ,
Based on my research, if you want to improve the performence, I suggest you use direct query or live connection and you could refer to below blog:
http://radacad.com/directquery-connection-in-power-bi-how-does-it-work-limitations-and-advantages
Regards,
Daniel He
Hi I have the same issue here I tried to import the adventureworks database from SSAS tabular 2016 but eventually got out of memory exception.
I even tried to reduce the import to only three tables less than 5k rows in total and this how much memory is used for 5k rows !
Any thoughts?
I think I found why import uses a huge amount of memory.
I ran ssas profiler to capture the runing queries when importing data and this is what queries the SSAS engine executes to retrieve the data:
For some reasons it seems to do a crossjoin between each column which leads to an exponentiel number of rows and rapidly generates an out of memory exception.
Has someone ever experienced such behavior before?
SELECT
{
[Measures].[Days Current Quarter to Date],
[Measures].[Days in Current Quarter]
}ON 0,
SUBSET(
//There were another 100 crossjoins here which I removed for the sake of readability
NONEMPTY(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
CROSSJOIN(
[Customer].[Address Line 1].[Address Line 1].ALLMEMBERS,
[Customer].[Address Line 2].[Address Line 2].ALLMEMBERS
),
[Customer].[Birth Date].[Birth Date].ALLMEMBERS
),
[Customer].[Commute Distance].[Commute Distance].ALLMEMBERS
),
[Customer].[Customer Alternate Id].[Customer Alternate Id].ALLMEMBERS
),
[Customer].[Customer Id].[Customer Id].ALLMEMBERS
),
[Customer].[Date of First Purchase].[Date of First Purchase].ALLMEMBERS
),
[Customer].[Education].[Education].ALLMEMBERS
),
[Customer].[Email Address].[Email Address].ALLMEMBERS
),
[Customer].[First Name].[First Name].ALLMEMBERS
),
[Customer].[Gender].[Gender].ALLMEMBERS
),
[Customer].[Geography Id].[Geography Id].ALLMEMBERS
),
[Customer].[Last Name].[Last Name].ALLMEMBERS
),
[Customer].[Marital Status].[Marital Status].ALLMEMBERS
),
[Customer].[Middle Name].[Middle Name].ALLMEMBERS
),
[Customer].[Name Style].[Name Style].ALLMEMBERS
),
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
User | Count |
---|---|
34 | |
32 | |
21 | |
11 | |
8 |
User | Count |
---|---|
53 | |
42 | |
28 | |
13 | |
11 |