June 4, 2008 at 7:31 am
Hi All,
Recently i involved myself in Finetuning work. I have reduced the execution time from 5 hrs to 30 minutes. I have to prepare a PPT file which has to show the problem faced while tuning and solution to that problems.
I have prepared a PPT file which contain 10 slides. I prepared like
Agenda
About XXXX application ( Due to security reason,i haven't mentioned my Appl name )
About XXXX Database
Uses of XXXX Procedure
What is the problem with this procedure ?
My Tuning approaches
Tuning Steps
About Tally Table ( I have used Tally table)
Problems faced
Solution
I have explained the above topic in the another slides. ( each topic has used 1 slides)
is that ok ?
Ideas are highly appreciable !
karthik
June 4, 2008 at 8:18 am
Seems like overkill.
Generally we approach it this way:
"Here are the top 10 poor performing procedures for database x"
"We have evaluated these procedures and identified possible fixes"
"Performance before the fix looked like this, performance after the fix looks like this and the total savings is some magic number"
"When do we deploy?"
Emphasis is on simple hard numbers. The only time we get into "What is this procedure used for" is when we find seriously questionable logic in the code of the query. Then we drill down on what the app is doing and start making suggestions for better approaches, either in the app or in the database.
That's my 2 cents and probably worth about that much.
"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
June 4, 2008 at 8:25 am
Who is your audience for the presentation?
What is the expected outcome from the presentation? For example, are you supposed to be justifying time spent, presenting a case for training so that developers will be able to write better performing code the first time.
If you are presenting to management, I'd leave out details of what, why, and how and focus on hard numbers like Grant said, and give some ideas on how to avoid problems like this in the first place.
If you are presenting to code geeks, then I'd spend more time on the code, what the problem was, how I identified it, the fix and why the fix is more efficient.
Not sure if that is what you are looking for but like Grant said that's my 2 cents.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
June 4, 2008 at 9:18 am
Less is more, use few slides, don't read them, put information on them you will talk about, but other than a way to keep people organized, I wouldn't use Powerpoint.
If the audience is technical people, pop open SSMS or your tools and show them how things changed and what works differently.
PPT is really a sales tool, not a technical explanation tool.
June 5, 2008 at 5:27 am
Who is your audience for the presentation?
My management.
how to brief 'Problem faced and solution' part ?
My question is
What are all the points comes under Problem faced ?
What are all the points comes under solution to that problem ?
Why i am asking is, say for example , i faced some problem while removing cursor and applying Tally table , but i have done it successfully. How should i brief it ?
karthik
June 17, 2008 at 8:21 am
I've found that if your audience doesn't really know what you're talking about, then you have to tell them what you're going to say, say it, then tell them what you just said... Kind of like Karthik did. The extra points of telling them about proper use of things like a Tally table further instill confidence in the audience that you might actually know what you're talking about... especially if you're new to a company like Karthik is...
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply