Viewing 15 posts - 16,531 through 16,545 (of 22,229 total)
You should evaluate Wait Stats. Andrew Kelly had an excellent little article in SQL Server Magazine recently. The Instanct Doc ID was 102111.
"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 16, 2009 at 9:23 am
Not being there, it's really hard to know after the fact, but on a guess... You had contention that was slowing down the rollback process. Then, when you rebooted, 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
September 16, 2009 at 9:14 am
hsac1301 (9/16/2009)
I have SQL 2005 server and because of the power failure, The databse has been corrupted. I have no backup at all.
I have tried
exec sp_resetstatus 'Net'
alter database Net SET...
"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 16, 2009 at 9:05 am
Baratella Marco (9/16/2009)
I have read something about parameter sniffing but I think my problem is a bit different.
I execute twice the same query with the same parameters:...
"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 16, 2009 at 8:52 am
There's no way to know for sure which it will do, but I'm fairly certain that the likely path is for it to simply use the compound index and then...
"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 16, 2009 at 7:28 am
Can you post an actual execution plan? And if you really want help rewriting the query, then sample structure and sample data should be supplied as well. Read the link...
"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 16, 2009 at 6:59 am
What you're describing sure sounds like a classic case of parameter sniffing. Do a search for that term and you'll find a lot of options for fixing it. Sometimes, 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
September 16, 2009 at 6:57 am
There are two ways it can do this, index intersection and index joins. It's not common for the optimizer to make these choices though. If you've got two indexes on...
"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 16, 2009 at 6:54 am
If you have a problem that you can document that you're seeing with memory, it'll be possible to help. Otherwise, there's very little you need to do with memory on...
"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 16, 2009 at 6:49 am
Huge topic and you're going to get disagreement from almost everyone one counter or another. Best approach is to start with simple, basic counters and expand from there. I'd focus...
"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 16, 2009 at 6:42 am
You can set the database to single user mode or, what I usually do, restricted user mode and use WITH ROLLBACK IMMEDIATE. That will remove all the connections and leave...
"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 16, 2009 at 6:36 am
You can get an idea of which queries use those indexes by using the execution plans available in the plan cache, yes. You should be able to run an XPath...
"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 15, 2009 at 12:13 pm
Inexpensive, Red Gate's SQL Compare. Fantastic tool.
"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 15, 2009 at 8:28 am
GSquared (9/15/2009)
"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 15, 2009 at 7:56 am
If you want short articles, I'd suggest doing a search in the Search box near the top of the screen here. There are a ton of articles on how 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
September 15, 2009 at 6:09 am
Viewing 15 posts - 16,531 through 16,545 (of 22,229 total)