Viewing 15 posts - 1 through 15 (of 17 total)
I've attached the actual execution plan containing the top 6 most time time-consuming queries and an Excel file containing more information about these queries taken from a couple of DMV's...
~ Just some guy trying to tune queries ~
May 3, 2017 at 8:17 am
Here's the code for the clustered indexes:
create clustered index cls_ix_stores_for_budgets on #StoresBudgets (storeID, ProgramID);
create clustered index cls_ix_tmp_report_final on #temp_report_data (store_ID, newSourceID);
The other columns in the SELECT and GROUP BY...
~ Just some guy trying to tune queries ~
August 8, 2016 at 8:14 am
I have tested adding the clustered index to the temporary tables and the overall time of running the stored procedure increased (unfortunately).
To be fair, the amount of time added is...
~ Just some guy trying to tune queries ~
August 8, 2016 at 7:41 am
Totally noobie mistake, I attached the wrong file. I replaced it with the correct file both in the original post and have attached it here as well.
~ Just some guy trying to tune queries ~
August 8, 2016 at 2:45 am
I'm sorry, I'm posting this issue on multiple websites, lost track a bit and forgot to mention it was a simplified version of the original query (that's why there are...
~ Just some guy trying to tune queries ~
August 8, 2016 at 2:29 am
Thanks for the suggestions, actually the query posted above is a bit obfuscated, changed column names / some aliases etc. but the obfuscation from SQL Sentry worked much better (didn't...
~ Just some guy trying to tune queries ~
August 8, 2016 at 2:11 am
ChrisM, I'm sorry but after a few discussions with my TL, I can't post the .sqlplan, due to NDA restrictions. Anyway, in the screenshots above table names have been changed...
~ Just some guy trying to tune queries ~
August 5, 2016 at 5:50 am
Ok, I will do so and post it here.
But if I look at the cached plans and this is the one whose last execution time was during the execution time...
~ Just some guy trying to tune queries ~
August 4, 2016 at 8:17 am
The execution plan is taken from:
, cast(qp.query_plan as xml)[Execution plan]
from sys.dm_exec_query_stats as qs
cross apply sys.dm_exec_sql_text (qs.sql_handle) as st
cross apply sys.dm_exec_text_query_plan (qs.plan_handle, qs.statement_start_offset, qs.statement_end_offset) as qp
And as per documentation, it doesn't...
~ Just some guy trying to tune queries ~
August 4, 2016 at 7:51 am
1. It's the actual execution plan, not the estimated. The execution plan from above is taken from querying the DMVs mentioned in my post.
The query that gives this execution plan...
~ Just some guy trying to tune queries ~
August 4, 2016 at 7:27 am
I'm curious as to why in the last example he used a LEFT OUTER JOIN, although in other queries in the article he used LEFT JOIN. From my knowledge, there...
~ Just some guy trying to tune queries ~
February 26, 2015 at 4:17 am
Very good article, but I have one comment though.
Possibly most people here know, but for those who don't, it's not dba.stackoverflow.com it's dba.stackexchange.com.
~ Just some guy trying to tune queries ~
January 6, 2015 at 12:34 am
rashedul.chowdhury (1/7/2014)
I created maintenance plan to delete backup files(3rd party backup named SQLSafe) more than 26 hours, but it is not deleting anything. Anyone has any idea or solution?
An alternative...
~ Just some guy trying to tune queries ~
September 28, 2014 at 2:11 pm
This is such a valuable thread! I have read all of your questions/answers and also searched on the internet for more possible best practices and I have wrote an article...
~ Just some guy trying to tune queries ~
June 30, 2014 at 2:51 pm
Hi,
There is an article which I've just recently found, article which details everything you need to do in order to avoid getting stuck in RESTORING state next time you do...
~ Just some guy trying to tune queries ~
March 23, 2014 at 10:47 am
Viewing 15 posts - 1 through 15 (of 17 total)