cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RobertG Frequent Visitor
Frequent Visitor

DirectQuery vs Import conumdrum

We've developed a Dashboard using the Import option.  I was naive to think that a move to DirectQuery would be easy. Subsequently I've realsied the difficulty in doing this as the queries to the data source are non-optimal and don't fit the mould for DirectQuery - they pull back too much data and I've got a nested join within my DAX code.

 

The easiest way around this would be for Microsoft to allow half houlry refereshes of the data with the Import option - why can't this be done?

Or I could have 6 versions of the Dashboard (i.e. 6*8=48) so I can have a least one upto date dashboard for each hhr during the day. 😉 

 

1 ACCEPTED SOLUTION

Accepted Solutions
RobertG Frequent Visitor
Frequent Visitor

Re: DirectQuery vs Import conumdrum

Thanks Eno for the reply.

 

I've been doing a bit of investigation and it looks as though you have do things 'properly' with DirectQuery. i.e write efficent queries and move as much as the processing into the SQL layer as possible. With DirectQuery you don't have the added luxury of preprocessing and shaping the data in the PowerQuery layer.

 

This just means more work which I had hoped to avoid. At least I'll be wiser next time.

View solution in original post

2 REPLIES 2
Super User III
Super User III

Re: DirectQuery vs Import conumdrum

@RobertG Have you tried to optimize the queries? Using views would also be a way to limit/shape the data set the way you need it using DQ. Even in the import scenerio it would be worthwhile so you don't pull extra data you aren't going to use anyway.


Looking for more Power BI tips, tricks & tools? Check out PowerBI.tips the site I co-own with Mike Carlo. Also, if you are near SE WI? Join our PUG Milwaukee Brew City PUG
RobertG Frequent Visitor
Frequent Visitor

Re: DirectQuery vs Import conumdrum

Thanks Eno for the reply.

 

I've been doing a bit of investigation and it looks as though you have do things 'properly' with DirectQuery. i.e write efficent queries and move as much as the processing into the SQL layer as possible. With DirectQuery you don't have the added luxury of preprocessing and shaping the data in the PowerQuery layer.

 

This just means more work which I had hoped to avoid. At least I'll be wiser next time.

View solution in original post

Helpful resources

Announcements
Exclusive LIVE Community Event #3 – Ask Arun Anything

Exclusive LIVE Community Event #3 – Ask Arun Anything

Join us in the third Triple A event!

Meet the 2020 Season 1 Power BI Super Users!

Meet the 2020 Season 1 Power BI Super Users!

It’s the start of a new Super User season! Learn all about the new Super Users and brand-new tiered recognition system.

Super User Challenge: Can You Solve These?

Super User Challenge: Can You Solve These?

We're celebrating the start of the New Super User season with our first ever Super User 'Can You Solve These?' challenge.

January 2020 Community Highlights

January 2020 Community Highlights

Make sure you didn't miss any of the things that happened in the community in January!

Top Solution Authors
Top Kudoed Authors