Viewing 15 posts - 20,926 through 20,940 (of 22,224 total)
You can run the query and capture the actual execution plan. There's a button on the default tool bar, look for the tool tip that says "Include Actual Execution Plan"...
"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 6, 2008 at 12:09 pm
Right now I'm trying to uninstall 2008 from a virtual machine.
For a good overview, read the book "Database Administration" by Craig Mullins. Best summary of the job I've ever seen.
Do...
"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 6, 2008 at 11:24 am
Well, back in the day... 6.5, 7.0, that was true, to a degree. But it hasn't been true at all for years & years now. Here's an introduction to performance...
"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 6, 2008 at 11:20 am
Yeah, sorry about that.
I sent an email to the group this morning. Did you get 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
March 6, 2008 at 10:47 am
Profiler and Perfmon are your bestest friends. There are also a number of dynamic management views available in 2005 that list missing indexes, etc.
"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 6, 2008 at 10:41 am
A seek is when a particular value (or values) is pulled out of an index. Think of it like looking up a particular index card (OK, people may not know...
"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 6, 2008 at 10:38 am
That's called RBAR (reebar) processing and means Row-By-Agonizing-Row. It's definately not the way to go in most cases.
Instead, you need to focus on the results that you want as a...
"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 6, 2008 at 10:28 am
ODAA caught by the coworkers, still not noticed by the boss or any one else in management.
"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 6, 2008 at 9:18 am
Oh great, I'm not schizophrenic enough. Now I have to figure out the order in which to read posts.
:w00t::w00t::w00t::crazy::sick:
"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 6, 2008 at 9:15 am
It's behaving pretty strangely over all. I'm seeing multiple alerts for discussions that don't appear to have any new posts at 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
March 6, 2008 at 9:09 am
First, NOT IN usually doesn't perform as well as an OUTER JOIN, so I'd change that right away. Second, you can check to see that values are a number by...
"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 6, 2008 at 9:06 am
Only because he wanted to return the values and lock them down from other users. So I did the SELECT with the update lock first, then udpate the table 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
March 6, 2008 at 6:22 am
Also, on the SELECT...INTO vs. CREATE TABLE & SELECT question. That one depends too. It depends on whether or not you are going to create indexes or in any other...
"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 6, 2008 at 6:11 am
Now you're being mean.
😎
"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 5, 2008 at 12:30 pm
Matt Miller (3/5/2008)
Jack Corbett (3/5/2008)
Matt Miller (3/5/2008)
It looked something like:
Matthew Miller
Senior Software Architect, O.D.A.A.
After I had been using it for...
"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 5, 2008 at 11:31 am
Viewing 15 posts - 20,926 through 20,940 (of 22,224 total)