Viewing 15 posts - 17,821 through 17,835 (of 22,219 total)
Yep. One at a time.
You can have a procedure that affects lots of tables, but that procedure will have individual statements for each table within 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
April 3, 2009 at 6:12 am
DISTINCT and GROUP BY are both methods of aggregating data. In general terms, neither is going to perform better than the other one.
In general practice, you need to structure...
"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
April 3, 2009 at 6:10 am
That is strange behavior. I've never seen anything like it. If you can, post the code. If it's huge, post it as an attachment.
Do you have lots of PRINT statements...
"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
April 3, 2009 at 6:06 am
Perry Whittle (4/2/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
April 3, 2009 at 6:04 am
I'm not sure, I haven't used this myself, and I don't see anything in the documentation. One point, Books Online suggests using the dynamic management function sys.dm_io_virtual_file_stats instead of...
"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
April 2, 2009 at 6:25 am
Yeah, I've read those. I was never completely dependent on IO, but it sure made me second guess even how much I used it.
But Gail was write to call me...
"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
April 2, 2009 at 6:09 am
I've never tried achieving that kind of measure before. But, I will say that you shouldn't be surprised if there are lots of reads even on a system that 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
April 2, 2009 at 6:02 am
I think he's referring to the statistics being out of date or insufficiently sampled. Just because you have auto-stats turned on doesn't mean that all the statistics are getting updated...
"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
April 2, 2009 at 5:48 am
GilaMonster (4/2/2009)
Grant Fritchey (3/27/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
April 2, 2009 at 5:38 am
Yeah, Barry's right, table variables aren't logged, but what is it that you're doing that's causing so much logging?
"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
April 1, 2009 at 7:34 pm
I think Gail has it right. They "fixed" the incorrect behavior from 2000. That leads to problems like what you encountered.
"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
April 1, 2009 at 8:14 am
I don't see it on her blog[/url]. It was in a presentation she gave at the PASS Summit last November.
"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
April 1, 2009 at 8:03 am
plavec (4/1/2009)
Tx for your help. We changed model and solved problem.But still I'd like to know if somebody knows how to makes compensation for FORCESEEK in 2005 or 2000.
Nice 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
April 1, 2009 at 7:57 am
Maybe I'm wrong. Wouldn't be the first time (today). Hang on, testing... might be a while.
"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
April 1, 2009 at 7:47 am
Regardless of default schema, if you don't reference the schema in the query, SQL Server will try to find the query in dbo. I don't think it's a bug. 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
April 1, 2009 at 7:19 am
Viewing 15 posts - 17,821 through 17,835 (of 22,219 total)