Viewing 15 posts - 17,986 through 18,000 (of 22,219 total)
Nah, blocking can be very isolated. It might be a particular page on the table that's slowing stuff down.
"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
March 18, 2009 at 8:13 am
Matt (3/18/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
March 18, 2009 at 7:46 am
Matt (3/18/2009)
I'd say about half and half, when listing PM's in the users inbox it uses the username, when displaying individual PMs it uses the id
Then it's going to be...
"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
March 18, 2009 at 7:14 am
First, just a word of caution, NOLOCK can lead to bad data. I don't just mean the ubiquitous "dirty read" meaning uncommitted changes, but I mean, extra rows, missing rows......
"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
March 18, 2009 at 6:28 am
Just a note of caution, running the Profiler gui on a production system can be very problematic[/url]. Best practice is to use a server-side trace to gather the data 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
March 18, 2009 at 6:15 am
Short answer, it depends.
Longer answer, you can reduce the number of round trips required to retrieve data and this can enhance performance. So instead of 3 seperate calls to 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
March 18, 2009 at 6:11 am
It sounds like you're getting a deadlock. You can take the advice offered and use a query hint to set the max degree of parallelism to 1 (MAXDOP = 1)....
"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
March 18, 2009 at 6:08 am
You say you have a problem when executing, but you're not saying what the problem is. Could you clarify further? Is it a performance issue within a query?
"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
March 18, 2009 at 6:04 am
Derek (3/17/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
March 18, 2009 at 6:03 am
I'm going to hell for this one, I just know it.
I was checking up on the status of what I think is a bug that I posted to Connect (Disabling...
"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
March 18, 2009 at 5:37 am
That's pretty inappropriate unless they're actively working on an upgrade which will come out shortly. VERY shortly.
"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
March 17, 2009 at 1:22 pm
It depends on the queries, but yes, indexes are extremely important. Most important is the clustered index. Here are several great articles on indexes by Gail Shaw [/url](GilaMonster). Even 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
March 17, 2009 at 10:31 am
If you're indexes are badly fragmented, it can take a while. You're not experimenting on a live production database are you? That's a recipe for disaster.
"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
March 17, 2009 at 10:29 am
GilaMonster (3/17/2009)
Bob Hovious (3/17/2009)
"We're running out of time!"Cannot run out of time. There is infinite time. You are finite, Zathras is finite. This is wrong tool.
Good one.
"You take, Zathras die....
"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
March 17, 2009 at 9:29 am
Time And Relative Dimensions In Space...
Of course, I do have a sonic screwdriver in my backpack, so I might be biased.
"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
March 17, 2009 at 9:05 am
Viewing 15 posts - 17,986 through 18,000 (of 22,219 total)