Viewing 15 posts - 13,126 through 13,140 (of 22,224 total)
Even though the database is in 80 compatibility, I'm pretty sure you can capture the exec plans from cache, so if the bad plan happens, snag it quick, jsut before...
"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 28, 2011 at 1:30 pm
Just a side comment, frequently when dealing with UNION, UNION ALL is a way of speeding things up, not slowing things down. If you're hitting problems, it must 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 28, 2011 at 1:29 pm
Not seeing the full plan, I can't guarantee my answer, but, if the operator accessing the cluster says that it's a key lookup operation, deferred or not, that's what it...
"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 28, 2011 at 1:25 pm
Glitch. Edited.
"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 28, 2011 at 1:20 pm
I find the deadlock graph in Trace can sometimes not provide enough information to really figure out what's up with some deadlocks. You might be better off using the data...
"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 28, 2011 at 1:19 pm
In terms of queries, the most important thing would be to write them well to begin with. I'd take a look at Itzik Ben-Gan's TSQL Querying book. There are some...
"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 28, 2011 at 1:15 pm
It's not a "known problem" it's a particular behavior. I'm not sure why some of the logs thought that there wasn't a full backup, but it's a switch that gets...
"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 28, 2011 at 6:37 am
dixon_dwayne (2/27/2011)
DNA_DBA (2/26/2011)
"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 27, 2011 at 5:43 am
wildfairy1 (2/27/2011)
"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 27, 2011 at 4:55 am
wildfairy1 (2/26/2011)
I am not sure if I have understand your statement fully here when you mention
"You should make sure that you're doing that as a batch, not as a...
"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, 2011 at 4:41 am
If you really are on an unreliable network, then most of the really stable and fast DR scenarios are not going to work too well for you. Log shipping might...
"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, 2011 at 8:33 am
I'm not familiar with Site Scope, but it looks like it only monitors the request end, not SQL Server itself. If the tool you're using is the same, then 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
February 25, 2011 at 8:25 am
Way too much unkown here. OK, so performance slows... in what way? Are queries running slower or are you getting fewer queries run? Have you looked at the wait statistics...
"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, 2011 at 5:46 am
I couldn't possibly tell you what to do without knowing what errors are involved. Check the SQL Server error logs. In Management Studio, expand the management box and it's under...
"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, 2011 at 5:40 am
That is the default functionality. I'm seeing it too.
Why not just type 'SELECT TOP (1000) * FROM MyTable' and then you can take direct control over everything that happens?
For a...
"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, 2011 at 3:10 pm
Viewing 15 posts - 13,126 through 13,140 (of 22,224 total)