Viewing 15 posts - 2,821 through 2,835 (of 22,227 total)
I was in your shoes 1 year ago and just studying is not...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 3, 2019 at 5:28 am
Specifically this stuff:
(covert(int,n.SSICatyear) = year(convert(int,ep.proceduredate)))
Is going to kill performance.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 3, 2019 at 5:13 am
In terms of overall impact to the server, I'd pick extended events over audit, every day. Audit is much more likely to have a negative impact on the instance.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 3, 2019 at 5:10 am
And, calculations like this are best done into a variable once:
@SearchTextLenght + @Q - 2
Having it in the filter criteria leads to problems.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 2, 2019 at 8:57 am
Just so the link to my book is on the thread...
Look below in my signature.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 2, 2019 at 8:29 am
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 2, 2019 at 8:28 am
Go with Muthukkamaran's advice. Change the Cost Threshold to a higher value and then leave everything else at the defaults until you see a reason to change through monitoring. "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 20, 2018 at 6:59 am
Maybe I don't understand what you're doing then. I don't know how you went from backups to Elastic Query as a way to solve a database refresh. Since the backups...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 20, 2018 at 4:49 am
Tac11 - Wednesday, December 19, 2018 10:04 AMThanks Grant, Any particular script do you suggest for compilation/recompilation trouble shoot?
Nope. Any script will compile or...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2018 at 1:16 pm
Change the query. Add the columns to the GROUP BY clause, or make it a sub-select or...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2018 at 1:15 pm
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2018 at 5:23 am
If you're using Azure SQL Database I'd look into the COPY DATABASE command in Powershell. That's going to let you capture a quiet copy of the database and then you...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2018 at 4:21 am
Look through the system views and you ought to be able to figure it all out. sys.dm_exec_query_stats has a number of values like sql_handle for finding statements and the plan_handle...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2018 at 4:15 am
So, automatically killing long running queries or queries that are blocking is a very bad idea. Can it be done? Certainly. There are a number of ways you could do...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 18, 2018 at 6:28 am
Or, since we're talking 2016, there's always:
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE CACHE
However, same rules apply. Don't do this in production.
You can also try using...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 18, 2018 at 6:10 am
Viewing 15 posts - 2,821 through 2,835 (of 22,227 total)