Forum Discussion
Troubleshooting slow cross-filtering
- Anonymous6 years ago
I've worked around the issue using the following method:
1. "Cache" the results of the direct query into a table on my database.
2. Change the query for the summary table to query the newly created table.
It is now working extremely fast, due to the speed of doing a simple select query against a database.
This adds the complexity of having to keep that table updated for the report users, but at least the performance is better!
Would still be interesting to learn how to optimise cross-filtering queries, struggling to find any good reference material online.
Anonymous , are taking data from both sources (import/direct) together. Can you share relationship diagram with Direct/import table labelled
After investigating using the performance analyzer I think I understand why the DirectQuery performance is important: it seems that the cross filtering does an entire query against the DirectQuery table, using an additional WHERE clause for each of the columns in the table visual.
Is there no way to tell the cross filtering operation to only use the StockCode column for cross filtering? To me it doesn't make any sense why it would query the rest of the columns, the only relevant column in this case is the StockCode column.