Viewing 15 posts - 11,671 through 11,685 (of 22,224 total)
Brandie Tarvin (11/15/2011)
Grant Fritchey (11/15/2011)
"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
November 15, 2011 at 6:29 am
Sounds like you guys covered it all better than I would have. Thanks!
"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
November 15, 2011 at 5:58 am
Hey everyone. Back from the hole into which I crawled. Did I miss anything? And no, I'm deleting a few hundred emails rather than read through all this. There'll just...
"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
November 15, 2011 at 5:52 am
-Syd- (11/7/2011)
"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
November 7, 2011 at 8:44 am
ionas (11/7/2011)
regarding your first issue. Every night we run a maintenance plan where we rebuild all indexes. By the way, since we rebulid is it necessary to Update statistics...
"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
November 7, 2011 at 8:35 am
And the answer is still the same.
"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
November 7, 2011 at 6:56 am
Execution plans are XML saved as a .SQLPLAN file. You can generate them, save them, and attach them, as is. All the data within will be transmitted. The preferred method...
"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
November 7, 2011 at 6:07 am
The question I'd ask is not which is faster for the insert, but which supports the SELECT queries better. You're going to load once an hour/day/week/year and then in between...
"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
November 7, 2011 at 6:01 am
Before we talk monitoring, let's validate your nightly process. You recreate your indexes and then update the stats? Is that right? If so, you might be hurting performance right there....
"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
November 7, 2011 at 5:55 am
Honestly, I doubt there's a single right answer to this. I don't know of anyone who, as a matter of routine, sets their identity values to be DESC. But if...
"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
November 7, 2011 at 5:49 am
There's Joe Sack's TSQL Recipe's. It's nothing but scripts and how to write them.
"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
November 7, 2011 at 5:47 am
Without more detail, it's hard to know for certain. For example, updating stats is good, but rebuilding an index also updates the stats, and with a full scan, not sampled....
"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
November 7, 2011 at 5:41 am
SQL Kiwi (11/4/2011)
SQLRNNR (11/4/2011)
What is this query plan operator?
It depends. It could be a hash join, hash aggregate, flow distinct, or a union...
Really? Looks like a car going into...
"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
November 5, 2011 at 11:20 am
It's highly unlikely that an index would change the results of a query. It looks like you have an extra space at the end of the line, which is why...
"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
October 25, 2011 at 4:54 am
Hard to know without seeing the query and knowing something about the data. Assuming no changes to the data and a well structured query, you should see the same data...
"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
October 25, 2011 at 4:52 am
Viewing 15 posts - 11,671 through 11,685 (of 22,224 total)