Forum Discussion
DirectQuery (bug?): all possible Date filter values are being output to SQL
I have a report with multiple visuals and 4 or 5 slicers on it, accessing an Azure SQL database via DirectQuery. Performance is worse than I would expect, and in debugging I'm noticing that sever...
I will internally forward your feedback here to relevant folks internally within the team and that should help prioritize the optimization higher on the backlog.
srinivt Do you know if Microsoft Team was able to research this more? This thread is over 2 years old but it's the best piece of information I've found reseraching my issue, which is exactly the same as what this thread was created for.
A 'date between' filter on my Date table sends over to sql every distinct date separately in the where clause. Modifying that line in the sql query it generates takes my result down from a few mintues to less than 2 seconds.
This could be the biggest item to make Direct Query more efficient with dates!