Event banner
Event details
Hey gregpetrossian, hopefully this is still going ahead (Unfortunately I may not be able to make it though as the time zone is a little out of whack for me)
Great overview of the options available in optimising our reports. I have two separate questions:
- When running Performance Analyzer in Power BI, do we need to first save the report on a blank page, reopen and then navigate to the page we want to analyse? Or is the "Refresh visuals" action good enough to analyse the relative performance of the visuals on the page?
- What are your top tips for new Power BI users for creating good performing DAX queries (especially if they have limited DAX knowledge)?
Also vote for Multi-row cards to have a vertical/horizontal orientation option (Microsoft Idea · Multi Row Card)
Thanks so much for your post Matthew! Hopefully timing works out and yes we are still on for tomorrow.
Hi gregpetrossian,
I have a sort of discussion type question regarding the Table vs. the Matrix visual. How much data is too much? And more importantly--how do you handle it when your audience wants you to fill either one with so many columns that you're scrolling right forever? I know how I handle it but would love to hear from others.
Another question for Marco. How much does Premium Capacity 'hide' badly performing reports versus 'shared' capacity?
Good day!
We would like to reduce the refresh time for one of our datasets. We're observing a 90 minute refresh duration using import mode for a dataset containing a fact table with ~250M rows. We're using premium capacity workspace (P1 SKU) with large dataset storage enabled. The data is being sourced from azsql (gen 5, 8 vcores) table with clustered column store index on fact table. Azsql CPU/data IO seems to stay under 20% utilization during the refresh. We've confirmed that a native query is being executed to refresh the fact table. We haven't pursued incremental refresh as the source table is trunc/load on daily frequency.
The fact table itself has fairly simple data types.
CREATE TABLE [dbo].[Fact_Table](
[c1] [int] NOT NULL,
[c2] [int] NOT NULL,
[c3] [date] NOT NULL,
[c4] [date] NOT NULL,
[c5] [varchar](1) NULL,
[c6] [int] NULL,
[c7] [date] NOT NULL,
[c8] [float] NULL,
[c9] [float] NULL,
[c10] [float] NULL,
[c11] [int] NULL,
[c12] [int] NULL,
[c13] [int] NULL,
[c14] [int] NULL,
[c15] [int] NULL,
[c16] [int] NULL,
[c17] [float] NULL,
[c18] [int] NULL,
[c19] [int] NULL,
[c20] [int] NULL,
[c21] [int] NULL,
[c22] [int] NULL,
[c23] [int] NULL,
[c24] [int] NULL,
[c25] [float] NULL
)Do you consider this scenario to be appropriate for import or have we reached a threshold where we should be considering DQ? We experimented some with DQ but encountered sluggish report performance and DAX limitations.
Any advice or troubleshooting suggestions would be greatly appreciated!
Thanks,
MK
