September 3, 2014 at 8:25 am
hi All,
can you please provide me some suggestion how to avoid this conflict.
1. Estimated rows are greater than actual rows.
2. Table insert cost is 30%. how to reduce this cost.
3. And also please provide some tuning tips for this procedure.
please find the exec plans and procedure scripts.
September 3, 2014 at 8:28 am
Duplicate post. Direct replies here. http://www.sqlservercentral.com/Forums/Topic1610013-360-1.aspx
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply