This past weekend, I had the privilege of doing a presentation at SQL Saturday #514 in Houston Texas. I had been to other SQL Saturdays before as both a participant and a “volunteer”; but I had never have spoken before.
Speaking in front of people is usually no big deal to me. I have been designing, presenting, hosting and administrating all types of training for the Boy Scouts for many, many years. I have taught Scouting newbies how to tie a knot to presenting on topics like “Project Planning and SMART goals” (email me if you want to know what SMART goals are). I have even coordinated an all day training event very similar to SQL Saturday for my Council called University of Scouting.
But what was different about this experience was the topic. I have been active in the Boy Scouts since I was eleven. I know Scouting information, concepts, and topics backwards and forwards. I have been facilitating trainings (presenting) since I was 15. So Scouting is 2nd nature to me. But presenting on SQL Server topics was somewhat nerve wracking. For me it was a test of not my presenting abilities; but my SQL DBA abilities. As an “Accidental DBA” I have always questioned my abilities with SQL Server. Everything I have learned about computers I have learned my self, so I am always 2nd guessing myself.
As a “First timer”, I thought it would be best to cover Beginning Level topics. My thought was 1) I knew the material and 2) after reading Tim Ford’s #EntryLevelChallenge it motivated me to remember my fellow newbies.
I won’t go into the topic of my presentation today as this is more about the experience. The audience, which I had 14 in attendance, was very attentive and I don’t think I put anyone to sleep!
I do need to work on my demos. They all worked as expected; but switching between laptop and projector, throwing SSMS on the projector screen, changing screen settings from duplicate to extend was all too much. There has to be a better way to switch between PowerPoint in presentation mode and SSMS to do demo. So I will practice that.
I thought I did best on time management. The time allotted was 60 minutes, I said “Thank you for your time” at 59 minutes and 30 seconds.
Over all the experience was well worth it. By the responses I received from the speaker evaluations, I think I did an OK job. I had no major criticisms except to slow down, I assure you that was nerves at the beginning.
This Saturday is SQL Saturday #514 in Houston, TX.
And this Saturday, I will be doing my first presentation at a SQL Saturday.
Luckily my presentation is in the morning so I can get it over with and enjoy the rest of the day. Otherwise, I probably would be stressing about it all day!
Hostile Takeover is my presentation on what do you do when handed the keys to a SQL server you have never seen. What information would you want to know and more importantly HOW do you get that information!
I will show some easy to use tools and scripts developed by people way smarter than I am. Heck, I will even show you how to hack into a SQL Server! As far as my website goes, I will update my slide deck and scripts repository after SQL Saturday! And hopefully I will find the time to upload the information to the SQL Saturday website!
A Legend is dead.
SQL Server 2005 is no longer supported. Today is the first day that DBAs and companies cannot call on Microsoft to help with or support a SQL Server 2005 Instance. (of course I am sure M$FT will gladly accept some money for additional support).
But many companies will still run with this stalwart and continue to use it until it dies. SQL 2005 has proven over time to be a stable system capable of doing a yeoman’s job.
Nine years ago, SQL Server 2005 revolutionized the way DBAs interacted with SQL Server. SQL Server Management Studio (SSMS) brought a new method of administering and programming SQL server. The Graphic User Interface (GUI) based program was miles ahead of the old Microsoft Management Console (MMC) plugin, SQL Enterprise Manager.
SQL Server 2005 was the first major overhaul of the SQL Engine, it introduced among other things XML data type, Common Language Runtime integration, and most importantly Dynamic Management Views (DMVs).
While some say “death to the dreaded GUI, long live T-SQL”, I for one, as a visual person, love the GUI. Yes, I always find myself using the “script” feature to learn the actual T-SQL and to execute the T-SQL for faster execution, but some tasks are made simpler using the GUI instead of T-SQL.
It definitely seems the development of SQL Server 2005 was directed by actual SQL developers, administrators, and users.
Over the years and versions, many features have been added to SSMS to even make it a better application: detailed graphical execution plans, intellisense, Central Management Server, the list could go on. I for one am excited that the Server Group has handed off SSMS as a separate tool because hopefully it can be placed on a more aggressive update schedule. Hopefully the development of SSMS will keep with pace of our needs.
So to recap, here is a list of SQL Server version still under main stream support:
- SQL Server 2012 – support ends 7/11/2017
- SQL Server 2014 – support ends 7/9/2019
That’s it, two versions!! (I did not include SQL Server 2016 on this list, because technically it has not been released for general use.)
Extended support, which only includes security updates is a little better:
- SQL Server 2008 & 2008 R2 – extended support ends 7/9/2019
- SQL Server 2012 – extended support ends 7/22/2016
- SQL Server 2014 – extended support ends 7/9/2024
Knowing how long it takes to get capital expenditures approved and how expensive SQL Server can be, you better start budgeting to replace SQL Server 2008 & 2008 R2 machines now!
This post is part of the challenge by Tim Ford (b|t) #EntryLevelBlogChallenge. Which of course is a personal challenge to technical bloggers to write one entry-level blog post a month over the next year and tag it on twitter with #iwanttoshare
All of by #EntryLevelChallenge post are tagged under “Back-2-Basics” category.
Today, I would like to talk about Maintenance Plans. This SQL feature is designed to allow DBA to automate maintenance tasks. Maintenance plans can be found under the “Management” folder in SSMS once you log into SQL Server. Right Click on the “Maintenance Plans” folder and select “New Maintenance Plan”
The quickest and easiest way to set this up is to use the “Maintenance Plan Wizard”. This is a step-by-step, check-box tool to setup everything possible with a database. The First Step allows you to name your maintenance plan and allows you to create the schedule you want to plan to execute on. This can either be one schedule for all jobs or individual schedules for each task. I would recommend individuals schedules because of the maintenance tasks can interfere with other tasks.
The next step to the wizard is where you actually pick which tasks you would like to run. Each task is given a brief description on the bottom in yellow.
- Check Database Integrity – uses the DBCC CHECKDB command to check the integrity of the database
- Shrink Database – AVOID USING THIS AT ALL COSTS. Shrinking databases on a regularly schedule actually does more harm than good to a database. If you are running out of drive space and shrinking databases must be done, please do it manually.
- Reorganzie Index – This task will defragment and compact your indexes on tables and views. There can be a performance gain, but the down side to this task is it is an “all-in” mentality. It will perform the task on an index whether it needs it or not.
- Rebuild Index – this task actually complete wipes index out and rebuild them so they are 100% new again. This task is also “all-in” approach and can be very I/O intensive.
- Update Statistics – statistics are the back-bone of the how the SQL Engine finds data. The SQL Engine uses statistics to determine the distribution of data in the data files. If statistics are out of date SQL may have to work harder to find data.
- Clean Up History – the execution and results of SQL Maintenance plans are stored in the MSDB system database. If this database is not kept in check it is feasible that it can grow uncontrollably.
- Execute SQL Agent Job – if you have built your own SQL Agent Job to do maintenance then you can actually execute it during this plan.
- Back Up Database (Full) – this does exactly what it says. This will perform a SQL Server FULL backup of the databases. This should be done on all databases including system databases.
- Back Up Database (Differential)—Differential backups are taken using this tasks. This can only be used for databases in FULL or BULKED LOGGED recovery model.
- Back Up Database (Transaction Log) – transaction log backups are crucial to “point-in-time” recovery of your database. It can only be used against databases in FULL or BULKED LOGGED recovery model.
- Maintenance Cleanup Task – this task should always be selected because it will cleanup any files left over by the execution of the plan.
The next step of the Wizard allows you to set the order of execution for the individual tasks you have selected. I prefer to always do Database Integrity Checks first, then indexes, then backups.
Finally you get to select which databases you would like this maintenance plan will execute against.
Depending on what tasks you select, there maybe follow up secondary tasks that you need to complete. Where to store reports, what files to clean up, etc. And then, click FINISH!
The Maintenance Plan Wizard is a simple way to setup maintenance plan. But do not fall into the trap of the “click-and-go” configuration. This is where you click all the check boxes and just keep clicking NEXT.
Please follow up and learn what each setup does and determine if you really need all the tasks. Many experienced DBAs will use custom scripts and custom maintenance plans for each type of database to ensure the SQL Engine does as little work as possible. The less time your SQL Server does performing maintenance tasks, the more time and resources it has to perform data tasks.