Viewing 15 posts - 6,436 through 6,450 (of 22,226 total)
If it says ALTER VIEW, guess what's happening. The deadlock error is not going to lie to 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
April 8, 2015 at 4:40 am
I'm with Luis. I don't like the normalization on DVD. I'll go one further, there is a movie (Luis used title) and there is the physical DVD itself. These are...
"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
April 8, 2015 at 4:39 am
But even with that filter, it's still going to show an execution count that is cumulative for the time that the query in question has been in cache. If 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
April 8, 2015 at 4:31 am
The TABLOCK is probably the way to go, but understand, you're likely to be blocked by processes that are reading from the table. You can't take that kind of lock...
"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
April 8, 2015 at 4:29 am
Exactly.
"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
April 7, 2015 at 8:41 pm
dwain.c (4/7/2015)
dwain.c (4/7/2015)
-- Some nitwit posting under the moniker of Dwain.C with a big fish for an avatar
-- gave me this...
"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
April 7, 2015 at 7:51 pm
It could be litespeed. It substitutes it's backup process for SQL Server, even if you're not calling it directly. Litespeed has a utility for unpacking backups to make them standard....
"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
April 7, 2015 at 7:49 pm
Yeah, that will reduce the number of values, but most people don't hit the issue. But, if you do, you can RESEED and set the seed to -1 and 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
April 7, 2015 at 5:21 pm
It means that even though you define the column as INT, if a given value would have fit within TINYINT, then that's what gets defined and stored for that value....
"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
April 7, 2015 at 4:22 pm
So a restore of the database on dev and the proc runs good, but in production the proc runs bad?
Sounds like a server setting and/or hardware then. Without that, I'd...
"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
April 7, 2015 at 4:14 pm
Do you have third party software installed on one of the servers for doing 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
April 7, 2015 at 3:54 pm
Can you restore the backup on the original server (if it's production, obviously, move it to a different database in the restore)?
"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
April 7, 2015 at 3:51 pm
You might want to go look at the documentation for SP3. Maybe there's something that if fixes that mess with restores from SP2. That's my best guess at the moment.
"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
April 7, 2015 at 3:47 pm
Yeah, everything that was between SP1 & SP2 will be included. Anything after SP2 will 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
April 7, 2015 at 12:24 pm
Deadlocks will present themselves as errors, not just a long running proc.
I agree it could be blocking. Check to see if there are blocking issues. Does your production server have...
"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
April 7, 2015 at 12:23 pm
Viewing 15 posts - 6,436 through 6,450 (of 22,226 total)