Viewing 15 posts - 18,556 through 18,570 (of 22,226 total)
John (1/30/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
February 2, 2009 at 6:15 am
kiman_keren (2/2/2009)
Dear Masters,I want to know, how to trace transaction? i want to trace insert query in an indexed column. Thx.
Usually it's best when you have a new question 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 2, 2009 at 6:01 am
Whoop!!!!
[holding up a lighter]
"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 2, 2009 at 5:57 am
Jeff Moden (2/1/2009)
Grant Fritchey (1/23/2009)
There are three ways you can do this easily. Use TOP, MAX or ROW_NUMBER.I'm thinking this one isn't about how to create the next id. 😉
Nah,...
"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 2, 2009 at 5:55 am
It looks largely pretty good. There are several key lookups and the four index scans at the top. For example one of the key lookups is against Customer_Canvasser and 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
January 30, 2009 at 7:37 am
You could upgrade to 2008 which has compression built in.
The other option that comes to mind is to compress them using, something, pkzip?, and then store them as a binary....
"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
January 30, 2009 at 6:11 am
RBarryYoung (1/30/2009)
Grant Fritchey (1/30/2009)
They're no good to me dead.Perhaps I can find new ways to motivate them.
Beware the wrath of the Fetts!
"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
January 30, 2009 at 6:07 am
Then, whatever it's doing, it's plodding along. You can kill it, but you might be waiting for a while for the rollback to clear.
"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
January 30, 2009 at 5:55 am
Usually save it as a .sqlplan file and then zip it up and post 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
January 30, 2009 at 5:50 am
Casper (1/30/2009)
Thanks for all your replies but I was now thinking: As mentioned it does UPDATES and INSERTS 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
January 30, 2009 at 5:41 am
Can you post the execution plans?
"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
January 30, 2009 at 5:39 am
They're no good to me dead.
"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
January 30, 2009 at 5:37 am
Things like this will lead to table scans, which will kill your performance:
WHERE
COALESCE(Last_live_insert_date, Last_booked_insert_date)
"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
January 30, 2009 at 5:14 am
Krishna (1/30/2009)
Why dont you run Profiler against the troubled server?Check the events:
TextData
ApplicationName
HostName
LoginName
EndTime
SPID
CPU
Duration
Reads
Writes
Profiler records when a proc, query or statement starts and when a proc, query or statement ends. 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
January 30, 2009 at 4:04 am
Except for the recursion, a CTE is really just a more sophisticated way to create sub-selects. So they're just as effective as the sub-selects were with the added value that...
"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
January 30, 2009 at 4:00 am
Viewing 15 posts - 18,556 through 18,570 (of 22,226 total)