Viewing 15 posts - 2,536 through 2,550 (of 22,227 total)
SQL Server will grab the amount of memory it has available and continue to grab more of that to the max. It does this completely automatically, stopping only at the...
"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
May 30, 2019 at 12:37 pm
Yeah, agreed. In fact, it's a great practice to have a different account administering SQL Server instances on the box and one administering the operating system. It's the right kind...
"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
May 30, 2019 at 12:30 pm
So, memory is different. What else? Number of processors? Max Degree of Parallelism? Cost Threshold for Parallelism? ANSI connection settings? These are just the top server settings that lead to...
"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
May 30, 2019 at 12:29 pm
You could keep a second copy of the database around. That will give you a comparison point. You have to sacrifice storage, but disks are pretty cheap.
"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
May 30, 2019 at 12:21 pm
Pretty much. Yes.
There are some exceptions. We're still working out how to deal with Azure SQL Database cross-database query setup. A couple of other issues along those very specific lines....
"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
May 30, 2019 at 12:17 pm
Nope. Just look at the logical reads. That's the amount of memory being used by the query.
"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
May 29, 2019 at 2:11 pm
It's likely that it's a version thing then, and certainly, likely to be 2014+ since that's when the cardinality estimation engine changed. Funny enough, Pinal's advice is the opposite of...
"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
May 29, 2019 at 12:43 pm
Thanks for the kind words. Really not doing that much, but thank you.
The easiest way to answer this question is to use Extended Events. The specific event you'd be looking...
"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
May 29, 2019 at 12:20 pm
It's to do the most efficient locking possible. Depending on what you're doing, a table lock may be more efficient. To be sure about all this, we'd need to gather...
"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
May 29, 2019 at 12:00 pm
There are lots of tools for doing health checks. I just found this one: https://mitchwheat.com/sqlfrontline/
"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
May 29, 2019 at 11:58 am
I'm somewhat aware of this, but I don't have the precise answer. It's some kind of bug or glitch in the optimizer that gets a difference in row counts. I...
"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
May 29, 2019 at 11:48 am
Good advice from "the warm-and-fuzzy DBA"
Ha! From the "I've burned way too many bridges and finally realize that throwing torches is a bad idea" DBA. I may learn slowly,...
"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
May 28, 2019 at 2:39 pm
I just can't believe some people. I requested our DBA to gather statistics from sys.dm_exec_procedure_stats in production and store them in a non-production database for analysis without compromising permissions....
"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
May 28, 2019 at 1:15 pm
The single best way to do this is through waits. What your server is waiting on is where your bottlenecks lie. Here is an excellent article showing how to...
"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
May 28, 2019 at 11:30 am
A health check is generally not done very often. A server health check is looking at the server configuration, settings, etc., to determine whether or not they are appropriate for...
"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
May 28, 2019 at 11:19 am
Viewing 15 posts - 2,536 through 2,550 (of 22,227 total)