Database Reference
In-Depth Information
<ClearCache
xmlns="http://schemas.microsoft.com/
analysisservices/2003/engine">
<Object>
<DatabaseID> --Database Name--
</DatabaseID>
</Object>
</ClearCache>
4. Highlight only this text and execute the query.
Note
You should run this query to clear the execution cache each time, prior to
running a test query, to measure performance.
5. Switch back to the SQL Server Profiler .
6. Select the last row for the Query End event.
7. Select and copy the entire row of text from the pane under the grid to the
clipboard.
8. Switch back to SSMS and insert a few more carriage returns to the bottom of
the query window.
9. Paste the query text from the clipboard.
10. Select only the new text and then execute the query.
There are other events you can add to a trace to get useful information. For example,
the Calculation Evaluation event returns detailed information about the execution
options the query engine uses for each stage of the query, but this information is very
verbose and can be time consuming to analyze.
Now you have a way to capture a query created by Excel or any other client tool and
then rerun the query in Management Studio. You can make changes to the calcula-
tion logic to test performance and results and then easily rerun the query. This can
be an invaluable technique to investigate how different tools are interacting with a
Tabular Model and generating a query script.
Search WWH ::




Custom Search