Viewing 15 posts - 17,986 through 18,000 (of 22,226 total)
RBarryYoung (3/18/2009)
Bruce W Cassidy (3/18/2009)
As a suggestion, go buy a collection of soft, squishy balls. Not only can you play with them as stress relievers, but 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
March 18, 2009 at 9:12 pm
Support cycles being what they are, if I were upgrading today (and I am), I'd be going for 2008, not 2005. At this point, it's four years into the 2005...
"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:41 pm
Compatibility mode is so that older or deprecated code continues to work on the new server, not so you can move backwards. Once it's formatted on the 2008 system, it's...
"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:37 pm
Unless, by chance, you're using the ordered GUID. It still fragments, but not as much.
"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 2:40 pm
Right there with you. I finally developed enough arm & shoulder strength to graduate to the 10lb sledge. Makes a HUGE difference. As you say, it'll fix or replace anything.
"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 12:43 pm
You don't need to cluster on the PK. Generally, the best place for the cluster is on the most frequently used access path. More often than not, this is 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 11:14 am
Matt (3/18/2009)
GilaMonster (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 11:06 am
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
Viewing 15 posts - 17,986 through 18,000 (of 22,226 total)