Viewing 15 posts - 6,691 through 6,705 (of 22,229 total)
Those are cross-database queries and not technically connections between the databases. First, I'd suggest reexamining your security to prevent that type of stuff if it's occurring in ways you don't...
"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
February 25, 2015 at 11:22 am
Yeah, I'd validate it by querying the cache directly using DMVs.
Nothing using WITH RECOMPILE? No one running DBCC FREEPROCCACHE? Nothing like that?
"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
February 25, 2015 at 7:18 am
Just a plus one to what Gail said. Better to capture diffs so you still have the accumulated values.
BTW, running it doesn't hurt, but if you ran it over and...
"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
February 25, 2015 at 5:35 am
Brandie Tarvin (2/25/2015)
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
February 25, 2015 at 5:33 am
Take a look at the wait statistics on the server to see what is causing things to run slow. Or, better still, capture the waits prior to a backup and...
"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
February 24, 2015 at 12:58 pm
If you're running a SELECT prior to the UPDATE, you might want to put an UPDLOCK hint on the SELECT. That way you take out the lock you want when...
"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
February 24, 2015 at 12:56 pm
I'd only capture the deadlock graph event to minimize the impact of trace. Better still, why use trace? You're on 2012. Use extended events. It has a smaller footprint and...
"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
February 24, 2015 at 12:53 pm
Jeff Moden (2/24/2015)
"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
February 24, 2015 at 12:47 pm
Jeff Moden (2/24/2015)
Brandie Tarvin (2/24/2015)
Jeff Moden (2/24/2015)
"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
February 24, 2015 at 12:46 pm
Depending on what you have for affinity, that may be limiting the number of processors being used and will give you a baseline to start from.
"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
February 24, 2015 at 5:41 am
The one technology built into SQL Server would be Merge Replication, but it's a nightmare to maintain and it requires every table taking part to be modified (you have 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
February 24, 2015 at 4:34 am
Yeah, new full backup. Any time you switch between simple and full you need to take a new full backup immediately after.
"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
February 24, 2015 at 4:29 am
I wouldn't say that's a precise art. You do know how much you're utilizing your current system. You can extrapolate somewhat from there. But, you also need to look at...
"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
February 24, 2015 at 4:26 am
Here's one of the simplest[/url] most straight forward formula's for setting your memory. Follow the recommendations here and you'll be fine in almost all situations.
"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
February 23, 2015 at 4:45 pm
Glad the book is helpful. You know where to go with questions.
I'm not aware of an explicit statement regarding forward compability, no. I know I've run into issues all 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
February 23, 2015 at 11:21 am
Viewing 15 posts - 6,691 through 6,705 (of 22,229 total)