Viewing 15 posts - 20,026 through 20,040 (of 22,224 total)
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
Nope.
You can use SSIS to do the work for you, but the analysis is up to 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
July 8, 2008 at 6:32 am
The only way I know of will hurt your performance. You can put FAST 1 hint on the query and it will start returning data immediately. It will however, really...
"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:30 am
Gail is on the money here, totally.
Instead of trying to avoid having multiple queries, accept the fact that you will have multiple queries and then get some code to generate...
"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:26 am
Posting the execution plan would help in the evaluation. Not seeing your structure and only seeing a query, we're all limited to making guesses.
"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:23 am
GilaMonster (7/8/2008)
"We fixed it. No thanks to you."
I can't honestly say that I wouldn't have hit the guy. Nice exercise in restraint.
"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 5:28 am
9 months at a start-up run by Harvard grads who's operating phrase was "Think Outside The Box." This extended to every single part of the company. One of the more...
"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 7, 2008 at 1:27 pm
It depends on the context that it's running under. If you're running it in a query window, it probably will return NULL.
Try this:
CREATE PROCEDURE ProcName
AS
SELECT OBJECT_NAME(@@PROCID);
GO
EXEC [ProcName];
You should see 'ProcName'...
"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 7, 2008 at 1:08 pm
SELECT OBJECT_NAME(@@PROCID);
"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 7, 2008 at 12:35 pm
Thanks for reminding me. That helped.
🙁
Crap! That was seven years ago.
"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 7, 2008 at 12:13 pm
Like everyone else, I'd suggest starting small. The best way I found to convince someone of the need to normalize was to find data that was messed up and 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
July 7, 2008 at 11:25 am
Viewing 15 posts - 20,026 through 20,040 (of 22,224 total)