Viewing 15 posts - 6,676 through 6,690 (of 22,219 total)
fdthompson35 (2/25/2015)
personid
personnum
fullnm
we want the following field from the ASSIGNPAYRULE TABLE
payruleid
where the personid from the PERSON table = the employerid in 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 26, 2015 at 4:14 am
It does, thanks. And Gail nailed it. You need to go the previous one.
"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 12:15 pm
Not that I'm aware of, no.
"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:56 am
You keep saying "restore during".
So, point of clarification for me. Do you mean you're going to try to restore the same database that a backup is being run against? Because...
"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:45 am
If it's saying your log backup is incorrectly formed, it might be corrupted. Try doing the restore without a stopat as a test. Oh, and not on the production box...
"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:24 am
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
Viewing 15 posts - 6,676 through 6,690 (of 22,219 total)