Viewing 15 posts - 19,081 through 19,095 (of 22,226 total)
Krishna_DBA (12/13/2008)
Why dont use DTA tool and apply the recommendations from there? I am just wondering.....
Primarily because it's unreliable. Your time is better spent learning how to do indexing yourself...
"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
December 15, 2008 at 6:29 am
Are the inserts & deletes done all the time or in discrete batches? If the latter, you can leave indexes off until you need them and then add them. 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
December 15, 2008 at 6:25 am
And you use this to reduce the number of calls back and forth between the stored procedure and the application calling 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
December 15, 2008 at 6:20 am
Also, by default, every proc exits with either a 0 for success or a 1 for failure as a return code on the proc. You can check for this in...
"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
December 15, 2008 at 6:10 am
So, if you run the TSQl to create your function, you can't see it? Are you looking through the GUI? If so, make sure you're hitting refresh. If you can...
"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
December 15, 2008 at 6:07 am
And here, the thread died, a horrible, messy death.
"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
December 15, 2008 at 6:05 am
IT isn't going away any time soon. If it does, we'll be far to busy eating each other to worry about where a pay check is going to come from.
"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
December 15, 2008 at 5:51 am
I guess I'm a bit in the middle. While, as an employee, I really don't want to see my job go away (really, seriously, I like my job, I need...
"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
December 15, 2008 at 5:49 am
To really answer the question, you've got to post the execution plans.
When updated statistics, did you use the FULL SCAN option?
"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
December 14, 2008 at 8:08 am
It's a pretty standard lookup table design:
LookupTable
LookupID Year Desc
1 1999 'Some important value'
2 ...
"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
December 14, 2008 at 8:02 am
Jeff Moden (12/13/2008)
I'm old... for me it's "may the farts be with you". Gives new meaning to the phrase, "It Depends". :hehe:
Oh no!
Mr. Bill!
"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
December 14, 2008 at 7:44 am
jcrawf02 (12/12/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
December 14, 2008 at 7:41 am
Thinking about it some more... how do you write a procedure...
Well, I assume that you know what you want to get, what data set you're looking for, first. Armed with...
"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
December 12, 2008 at 4:45 am
If I understand the question, I guess it's something I do every day (all day sometimes). First, I need to have a set of working parameters. Preferably, I have some...
"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
December 12, 2008 at 4:43 am
You have a single transaction where you are mixing INSERT/UPDATE and SELECT? Be very careful that you're performing these actions in the same order or you'll be getting deadlocks 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
December 12, 2008 at 4:31 am
Viewing 15 posts - 19,081 through 19,095 (of 22,226 total)