If you have been considering entering yourself in the Exceptional DBA Awards this year, or nominating a DBA you know, don’t procrastinate much longer, as the last date you can enter is July 10, 2009.
I am one of four judges who will be selecting the nominees, and I want to offer several bits of advice about entering the contest.
If you have any questions about the contest, please ask them here, and I will try to answer them.
I was recently talking to a friend from the U.K about how much notice a DBA should give to their employer should they decide to resign. I told him that the general practice for the U.S. was two weeks, but of course this could vary if the DBA signed an employment contract that stated a shorter or longer notice period.
He was surprised to here that only two weeks notice was standard. He expected it to be longer because of the importance of most DBA positions, and the common difficulty of replacing a DBA position in a timely manner. Then I got to thinking, in the several full-time DBA jobs I have had, two weeks notice was what the organizations I had worked for requested. Then I thought some more. I had answered by friend’s question based on my own personal experience, not based on any facts I had.
Next, I decided to see if I could find any facts about the typical resignation notice that DBAs give their organizations, but I couldn’t find any data on this. I guess its not the kind of data people research and publish.
So, here’s my question to you. Based on your past and current jobs as a DBA, has a two week resignation notice been the norm, or not? It will be very interesting to see what various DBAs experiences have been.
In the last year or so, there have been a lot of articles, blog entries,and forum posts on the kinds of technical questions hiring managers can ask a prospective DBA candidate in order to determine their technical proficiency. While technical skills are important for a DBA, I think a lot of hiring managers place too much emphasis on hard technical skills, and don’t place enough emphasis on the characteristics (personality traits) that DBAs need to have in order to be successful. In the rest of this blog entry, I want to suggest some characteristics that I think all DBAs should have.
Below, I have listed each characteristic, a brief explanation of it, and three questions you might consider asking that can help you tell if if a job candidate has that characteristic or not. While some of these questions include technical aspects about being a DBA, what you are wanting to determine is how well the job candidate fits a particular characteristic, not to judge the technical part of their response. There are no wrong or right answers below. What you are looking for is to see if the job candidate has the characteristics that you think make for a good DBA, and by asking these kinds of questions, you will be one step closer in determining if a particular candidate is best for your organization.
Enjoys Technology: If a DBA doesn’t enjoy technology, what’s the point of being a DBA.
Enjoys Challenges: A DBA’s life is once challenge after another. If a job candidate doesn’t like challenges, then he shouldn’t be a DBA.
Good with Details: A DBA’s job is all about small details, and doing them correctly.
Embraces Change: A DBA’s work is always changing, and you want someone who can keep up with fast-paced change.
Enjoys Learning: Database technology is constantly changing, and a successful DBA must keep current.
Accepts Responsibility: DBAs take on a lot of responsibility, whether they realize it or not.
Maintains Professionalism: I define professionalism as respect for others in an organization, which is important, as DBAs often work with a lot of different people.
Trustworthy: DBAs are privy to many company secrets, and you want to ensure that they are capable of keeping them.
Dependable: If you can’t depend on someone, who wants them around?
Can Work as Part of a Team: DBAs are almost always part of a larger team, and need to know how to work well with others to accomplish common goals.
Can Communicate Effectively: DBAs have to communicate with many different people to successfully execute their job.
Listens Well: Listening is just as important as communicating.
Realistic: DBAs need to be realistic about what they can and cannot do given the resources they have available to them.
Patient: Many DBA tasks take a long time, or it takes time for decisions to be implemented. DBAs must understand that patience is an important virtue.
Enthusiastic: You want a new DBA to land on his feet running when he starts his new job, and being enthusiastic about the job, and about being a DBA, is a good sign of this.
This is a long list of characteristics and questions, and if you asked them all, your interview might take hours. If you are a hiring manager, I suggest to pick out those characteristics above that are most important to you, and then ask the job candidate several questions about them. In some cases, you will know right away if a candidate meets the characteristic, and other times, you may have to follow up to be sure. In any event, by asking these kinds of questions, in addition to technical questions, you will end up with better information in which to select the best candidate for the job.
I am working on the outline of a new book I am writing, tentatively called Mastering SQL Server Database Maintenance. It will loosely be based on a similar presentation I give at user groups and conferences.
If you have the time, I would like to get your opinions on one or more of the following topics.
1) Who should the book be targeted to? Who would benefit most from reading such a book?
2) Should the book focus on getting the most out of the Database Maintenance Wizard, should it only mention the Database Maintenance Plan in passing, or should it ignore the Database Maintenance Wizard completely?
3) Should the book emphasize using the Management Studio GUI to get work done, or should it emphasize using T-SQL scripts, or a combination of them both?
4) What topics do you think should be included in the book? Below I have provided a “starting” list. Do you think these topics are important, or not? What topics have I left out?
5) What other suggestions do have for such a book?
If you have the time, I would greatly appreciate your feedback. Thanks.
The DevTeach/SQLTeach keynote was from Tim Huckaby, founder of InterKnowlogy.
DevTeach/SQLTeach was held this past June 8-12 in Vancouver, BC at the Four Seasons Hotel, located directly in the middle of Vancouver’s vibrant city center.
The event offered 8 different tracks (two for SQL Server) and had 58 different speakers presenting over 120 sessions, making this event the largest independent developer and DBA conference in Canada.
I was fortunate to make four presentations at SQLTeach, including: How and When to Implement Indexed Views, How to Use SQL Trace, Using SQLDiag to Troubleshoot SQL Server Problems, and Detecting and Troubleshooting Memory Bottlenecks.
Other SQL Server speakers included such notables as Peter DeBetta, Bill Graziano, Kevin Kline, Jessica Moss, Roman Rehak, Joe Webb, Hugo Shebbeare, and many, many more.
The next DevTeach/SQLTeach will most likely be held in Toronto, June 2010.
Rodney Landrum, SQL Server MVP, and Karla Remail, coordinator of the Pensacola SQL Saturday, give out prizes at the conclusion of the event.
The first SQL Saturday to be held in Pensacola, FL was held Saturday, June 6, 2009 at the Pensacola Junior College, and attracted 173 attendees from several different states. There were five simultaneous tracks with 34 different session from 31 different presenters,including Steve Jones (Editor of SQLServerCentral.com), Andy Warren (founder of the SQL Saturday events), Brian Knight, Rodney Landrum, Jessica Moss, myself, and many more.
The event was coordinated by Karla Remail, the leader of the Pensacola SQL Server users group, and many volunteers. The event was such a success, that the next one has already been planned for Saturday, June 5, 2010, which will also include several non-SQL Server tracks, such as .Net and SharePoint.
I have spoken at many conferences over the years, including the PASS Community Summit and SQL Server Connections, and one of the things I have noticed is that there is very little overlap between the DBAs and developers who attend each of these conferences. There seems to be a group who likes to attend the PASS Community Summit, and another group who likes to attend the SQL Server Connections conference.
In the past, and still today, SQLServerCentral.Com is a strong supporter of the PASS Community Summit. But because of the lack of overlap between these two conferences, we feel that we have been missing out on supporting those DBA and developers who choose to attend the SQL Server Connections conference. Because it is our goal at SQLServerCentral.Com is to be as inclusive as possible, SQLServerCentral.Com has now teamed up with SQL Server Connections to present our own SQL Server track at the conference. This will give us the opportunity to reach out to an entirely different group of DBAs and developers who we don’t normally interact with.
If you are not familiar with SQL Server Connections, it is part of a larger conference called DevConnections that is put on twice a year by Penton Media (they same people who publish SQL Server Magazine.) The annual spring event is held in Orlando, FL, and the annual fall event is held in Las Vegas.
The umbrella DevConnections conference include multiple, simultaneous break-out conferences, which include ASP.NET Connections, SharePoint Connections, Visual Studio & .NET Connections, and of course, SQL Server Connections. When you sign up for one event, you can attend any of the sessions among these concurrent conferences, which give attendees a rich learning experience.
The next SQL Server Connections is going to be held November 9-12, 2009, at the Mandalay Bay Hotel and Conference Center in Las Vegas, NV, and will follow this schedule:
Monday, November 9, 2009: Two SQL Server pre-conference workshops:
Tuesday, November 10, 2009: Microsoft Day:
Wednesday & Thursday, November 11-12 2009: SQL Server Connections and SQLServerCentral.Com Tracks
Friday, November 13, 2009: One SQL Server post-conference workshop:
For a list of all the speakers, you can visit this webpage, and for a list of all the sessions, you can visit this webpage.
The SQLServerCentral.Com track includes five speakers presenting a total of nine different sessions. If you recognize any of the speakers, that is because you have probably seen their contributions to the SQLServerCentral.Com and Simple-Talk websites. They include:
Joe Celko served 10 years on the ANSI/ISO SQL Standards Committee and contributed to the SQL-89 and SQL-92 Standards. He has written over 800 columns in the computer trade and academic press, mostly dealing with data and databases. He is author of seven books on SQL for Morgan-Kaufmann: SQL FOR SMARTIES (1995, second edition 1999, third edition 2005), SQL PUZZLES & ANSWERS (1997), DATA & DATABASES (1999) and TREES & HIERARCHIES IN SQL (2004), SQL PROGRAMMING STYLE (2005) and ANALYTICS & OLAP IN SQL (2005) and THINKING IN SETS (2008). Joe will be presenting two session: Darling, Your SQL is Sooo Last Season! and Naming and Modeling Data Objects.
Grant Fritchey, Microsoft SQL Server MVP, works for an industry-leading engineering and insurance company as a principal DBA. He’s done development of large-scale applications in languages such as Visual Basic, C#, and Java, and has worked with SQL Server since version 6.0. Grant spends a lot of time involved in the SQL Server community, including speaking, blogging, and he is an active participant in the SQLServerCentral.Com forums. He is the author of SQL Server Execution Plans (Simple Talk Publishing, 2008) and SQL Server Query Performance Tuning Distilled (Apress, 2008). Grant will be presenting two session: Scouting Out Execution Plans and MUQT: More Unnecessary Query Tuning.
Brian is a SQL Server author, columnist, and Microsoft MVP, focusing primarily on SQL Server security and administration. He currently serves as a database administrator / architect for a large bank where he can concentrate on his passion: SQL Server. He is a contributing author to How to Cheat at Securing SQL Server 2005 (Syngress) and Professional SQL Server 2008 Administration (Wrox). In the technical community, Brian is president of the Midlands PASS Chapter. Not only is Brian an active blogger at SQLServerCentral.Com, he is a prolific forum participant and is one of the top forum posters on the website. Brian will be presenting two sessions: Keeping on Top of Your SQL Server Using Dynamic Management Objects and Catalog Views and Best Practices in SQL Server 2008 Configuration Management.
In the months ahead, I will be doing interviews with all of these speakers so that you will get the opportunity to learn a little more about them.
Share this post :