Viewing 15 posts - 20,011 through 20,025 (of 22,219 total)
From my own experience and everything I've read, no, the order doesn't change the selectivity. It will affect sorting speed. If you need to retreive the data in a particular...
"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
July 10, 2008 at 6:44 am
The data in an insert trigger is contained in a set called INSERTED that you can treat just like a table. So if you wanted to capture the data all...
"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
July 10, 2008 at 6:35 am
You would have to use a user defined function as Chirag mentions above. Doing that in the where clause is pretty likely to lead to RBAR (row-by-agonizing-row) processing, which kills...
"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
July 10, 2008 at 6:31 am
If you limit the events captured to only what you really need (especially staying away from capturing individual statements) and you use the extended stored procedures to fire off Profiler...
"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
July 10, 2008 at 6:26 am
A bit of both really. Plus, if you haven't been here, you might not know. This place is kind of big. There's a lot of empty space and we tend...
"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
July 9, 2008 at 9:35 am
It really depends on where you're driving to as well as the distance. I used to commute about 30 miles down I-90, the Massachusetts Turnpike, and it took about 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
July 9, 2008 at 9:30 am
We have very similar requirements. We do it like this:
SELECT...
FROM MyTable m
WHERE m.VersionId = (SELECT TOP(1) m2.VersionId
...
"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
July 9, 2008 at 7:10 am
Brian Tax (7/8/2008)
"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
July 9, 2008 at 6:26 am
How come you don't need to add the scalar operator, '0 [Basic]', to the * version of the query? If you did add that, would it change the execution time?
Jeff...
"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
July 8, 2008 at 1:13 pm
I'd need to see the execution plans to be sure, but I'll be you're getting index lookups for the column list, but not for the SELECT *. Can you post...
"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
July 8, 2008 at 12:04 pm
Steve Jones - Editor (7/8/2008)
"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
July 8, 2008 at 11:58 am
Honestly, I think it's a crutch. I haven't seen a well-planned design use 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
July 8, 2008 at 9:30 am
Some are friends, some aren't.
That about sums it up. I do agree that avoiding the occasional excess drinking when it occurs is a good choice if you want to move...
"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
July 8, 2008 at 7:29 am
Based on nothing by my own personal experience...
What getting into Harvard gets you, these days anyway, isn't a superior education, but a superior name. You're a Harvard Grad (capitols required)....
"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
July 8, 2008 at 6:59 am
I got this wrong as well. I've seen both STATIC & FAST_FORWARD work better in different circumstances. "It Depends" should have been the right answer on this one.
"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
July 8, 2008 at 6:38 am
Viewing 15 posts - 20,011 through 20,025 (of 22,219 total)