ny sugestions to improve peroformance ?
There are some things here that I'm not sure you can make better - parsing JSON, for example, there is no magic in SQL Server 2014. I would start by getting rid of the table variables. For better input, please generate an actual plan from within Plan Explorer - this will add runtime metrics and other data you don't get when you open a plan generated in Management Studio (especially an estimated plan).
thanks for the feedback.
i've attached the plan (XML)
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 x664
plan explorer upload x474
execution plan x121
poor performance x111
stored procedure x20
asked: May 08, 2017 at 10:42 AM
Seen: 69 times
Last Updated: May 09, 2017 at 07:25 AM
How can I improve this stored performance?
Same Query, Two Plans, One Stinks
Component running slow
Is there a better way to search for matches
Execution plan mystery
How can I improve this plan. Table Insert is costing the most at 84.6% - can it be improved ?
Any idea why the filter limiting to 5K instead of 320K rows is done at the end ?
Stored procedure randomly using bad execution plan
A filter with the attached query causing slowness and performance issues
Trying to understand why partition elimination is happening in some plans, but not others
© 2013 SQL Sentry, Inc. All rights reserved.