Viewing 15 posts - 14,266 through 14,280 (of 22,219 total)
Yeah, late to the game, I was going to suggest READ COMMITTED SNAPSHOT as well.
Isolation levels are very different from locking hints. Isolation levels define how transactions will behave...
"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
September 29, 2010 at 8:58 am
Stefan Krzywicki (9/29/2010)
"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
September 29, 2010 at 7:59 am
Yes, READ COMMITTED is the default. Well, I'm stumped then. Something that is just a SELECT shouldn't be grabbing exclusive locks, so the best thing I can suggest is...
"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
September 29, 2010 at 7:54 am
GilaMonster (9/29/2010)
Brandie Tarvin (9/29/2010)
Secondly, he should be asking you what he can do to facilitate what you're doing. Not badgering you about the fact that you're behind schedule.
An extension 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
September 29, 2010 at 7:28 am
scott_lotus (9/29/2010)
1) I thought SELECTS exclusively...
"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
September 29, 2010 at 7:15 am
Matt S. (9/29/2010)
I hear you. I've seen DBAs light up with some glimmer of hope when I'm hired to reign in developers gone wild. It's because I sell my services...
"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
September 29, 2010 at 7:12 am
Brandie Tarvin (9/29/2010)
GilaMonster (9/29/2010)
* Asks the developers what they are currently busy with
* Updates his % completed...
"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
September 29, 2010 at 7:01 am
Matt S. (9/29/2010)
"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
September 29, 2010 at 7:00 am
Grant Fritchey (9/29/2010)
"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
September 29, 2010 at 6:58 am
Personally, the easiest would be to put SQL Server Integration Services to work on it. SSIS can do this type of break down quite easily.
Another option, not as easy, would...
"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
September 29, 2010 at 6:56 am
For it to simply stop execution I'd expect an error or message of some sort. However, to try to figure it out, I'd wrap the statements in a TRY/CATCH block...
"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
September 29, 2010 at 6:52 am
Yeah, I'd add a few counters to that.
SQLServer:Buffer Manager:Page Life Expectancy
SQLServer:Buffer Manager:Lazy writes/sec
SQLServer:Memory Manager:Memory Grants Pending
Memory:Pages/sec
Memory:Page Faults/sec (really useful for trend analysis)
Memory:Pages Input/sec
Memory:Pages Output/sec
If you want to know if...
"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
September 29, 2010 at 6:47 am
If the query is for reporting only, why would it be taking out an exclusive lock on the index? Are you sure that the query isn't doing some type 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
September 29, 2010 at 6:42 am
Just to reiterate, since you bounced the server, there's no real recourse for identifying an issue other than the error logs. That is, unless you put some type of monitoring...
"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
September 29, 2010 at 6:40 am
What are you trying to do? There are ways to create temporary tables (as is shown above), table variables, and you can create permanent tables, all on the fly. So...
"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
September 29, 2010 at 6:38 am
Viewing 15 posts - 14,266 through 14,280 (of 22,219 total)