millions of rows generated in hash operator, how to avoid this
Can you provide the definition of the view? I can see which tables are involved from the join diagram tab, but I can't see what else the query in the view might be doing to produce the problematic merge join with 17 million rows of output.
Up to 50 attachments (including images) can be used with a maximum of 209.7 MB each and 209.7 MB total.
Answers and Comments
query plan x692
sql sentry upload x39
data islands x1
asked: Nov 27, 2017 at 03:07 PM
Seen: 44 times
Last Updated: Nov 30, 2017 at 05:46 PM
Sort Operation Performance
Why does changing an account name field change the execution plan so much?
Any idea why sp_MSdistribution_cleanup is so CPU intensive?
What should I look at to begin understanding the sudden performance degradation of this query?
CPU Spike Randomly due to SQL queries
Why does the Clustered Index Seek take 45% of plan?
Required Inputs on the Execution Plan
Having problems understanding what what can be improved
© 2013 SQL Sentry, Inc. All rights reserved.