Presentations – Lessons Learned

Categories: News, Professional
Comments: No Comments
Published on: January 14, 2010

This will be a very short entry.  I just wanted to share a few things  I learned very quickly while prepping for my most recent presentation for SSSOLV (Las Vegas PASS).

First, while doing the slides and testing the SQL, it dawned on me that I could probably fix one of the flaws in my first presentation very easily.  I did some checking and voila – it was indeed a very easy fix.  The problem that needed fixing was readability of SQL code on screen during presentations.  I tried using the magnifier, but that was horrific.  So for that presentation, I dealt with it.  It was very aggravating.

So, how did I fix it for this time around?  I changed the font size.  From SSMS, click tools and then options.  Under the environment option, select Fonts and Colors.  There is a Size dropdown menu on the right.  I changed that setting from the default of 10 to 20.  The code was plenty big to read now.

The same can also be done for the results.  Just change to “Grid Results” in the “Show Settings For” dropdown.  The default is 8, I just double this to 16.

Changing the “Grid Result” setting does require a Restart of the “Grid Result” which turned out to be a Management Studio restart for me.

Second, was something that ticked me off while prepping the slide deck.  I didn’t have an issue with this during the last presentation, and it was a monstrous issue this time around.  Sometimes it is nice to add custom animations to the slides to help hide and reveal items as you progress through the discussion.  The animations on images were not working.  The images were just laying on top of each other, doing nothing and looked like crud.  This too, is a simple fix – though tedious.  To get an image to perform the custom animation, it must be an attached image.  A pasted image will not work.  Once the image is saved as a “jpg” for example and then attached to the slide – the animation will work as expected and the slide will look more professional.

Third, to help the presentation flow, is to make sure all SQL connections are open and running.  I thought I was ahead of the game by having all of my scripts open in SSMS and ready to go in the order that I need them.  Well, my system went to standby while waiting for my turn to present.  When the system went to standby, all of my connections closed.  I didn’t think of this prior to starting my presentation.  This too is easy to fix – it just requires a mental note.  Prior to starting the presentation, and even prior to plugging in the connector for the projector – verify the connection state of any open scripts in SSMS.

Fourth, to save any embarrassment, run through your slides one more time close to presentation time.  Make sure they make sense.  Make sure any thoughts you want to bring up are noted on the slides or can be keyed from something on the slides.  And verify the look, flow, feel, and function of the slides.  The slide deck could be a useful tool along with any scripts to distribute to the group.  You will want to know that they are flawless.  Consider this as your final opportunity to edit and revise.

Lastly, build in some question and answer segments.  Invoke the group to participate.  Get them to help carry the presentation.  This will not only  help save your voice, but it will also help the group to stay in tune with the presentation.  This is less of a lesson learned, and more of a reminder.  I try to do this in any setting where I may be presenting (school, church, job).  This can easily be done with a slide insert labeled “Discuss” or “Why” or “Questions.”  Anything that will remind you and notify the group that interaction is forthcoming.

No Comments - Leave a comment

Leave a comment

Your email address will not be published. Required fields are marked *

January 2010
« Dec   Feb »


  • @MidnightDBA: Server: No SSMS, no powershell, SQL 08 r2. Best TSQL script to create sp_add_job statements, et al, for all jobs on the instance? #sqlhelp
  • @AMtwo: @ajneuman AFAIK, the only way to upgrade is to point SSRS at the DB, and let it do it's thing. What error do you get on upgrade? #sqlhelp
  • @ajneuman: Is there a way to manually upgrade the Report Server databae? It's failing to upgrade from version 147 to 174. #sqlhelp #SSRS #sqlserver2016
  • @AngryPets: @SQLYard #sqlhelp Nope - they just need to be sized to handle the indexes on them. I'd check file stalls vs all files to see if helping/etc.
  • @SQLPrincess: #sqlhelp Any ideas on how to reverse engineer a data flow diagram from queries to show the data transformations?
  • @SQLYard: @AngryPets Thnks so the 3 filegroups different sizes are normal then? I was thinking they needed to be aligned in size. #sqlhelp
  • @AMtwo: @SqlRyan If you want to use source control with your report designer, use Visual Studio + SSDT. #sqlhelp
  • @AngryPets: @SQLYard #sqlhelp [2/2] storage, they aren't as helpful as they could be in 'spin disk' days. But still have benefits. Can be over-used.
  • @AngryPets: @SQLYard #sqlhelp Index filegroups are/can-be a best practice - depending upon data, load, and IO subsystem. With more modern ... [1/2]
  • @SQLYard: Index Filegoups? I took over a server that has 3 index filegrps. 1 grp is Lrge seems other 2 rnt being used.whts best pract on this #sqlhelp

Welcome , today is Friday, September 30, 2016