Viewing 15 posts - 16,516 through 16,530 (of 22,221 total)
WAY back on SQL Server 6.5, we had to schedule a reboot once a week because that version of SQL Server and the Windows operating system back then were 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 17, 2009 at 6:40 am
From what I can see, it looks like REPAIR_DATA_LOSS has fixed the issue (at what cost, you have yet to find out). What problem are you having after running 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 17, 2009 at 6:14 am
forum member (9/16/2009)
I am still confused,whether to go ahead with lock or no lock on queries for example while one user is booking a product or editing a product...
"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 17, 2009 at 5:33 am
BobMcC (9/16/2009)
I have a user that needs access to one of my databases with a query 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 16, 2009 at 5:06 pm
Especially when you're talking about some huge long running query, a little bitty thing could cause contention with it, yeah. It's entirely possible that one process caused the other problems.
"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 12:43 pm
Ah, well, hard to know then, but I'd still be inclined to some kind of blocking. It makes the most sense based on the evidence. If it happens again, 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
September 16, 2009 at 11:33 am
Did you look at the server to see if there were other processes running, other connections with locks?
"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 10:34 am
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
Viewing 15 posts - 16,516 through 16,530 (of 22,221 total)