I recently ran across the following scenario. A SQL Server instance had been upgraded from SQL Server 2005 to SQL Server 2008. At the same time, the older physical hardware had been replaced by newer hardware. The DBA who had set up and configured the older server was no longer at the organization, and a new DBA had performed the upgrade. After the upgrade was completed, I was asked to review its configuration. I started by reviewing the various server and database settings, along with the assorted database maintenance jobs, and then I began to ask questions about them.
Monthly Archives: January 2010
SQL Source Control Early Access Program Open
Managing T-SQL source code has never been easy, and has often been the bane for many T-SQL developers. Later this year, this problem will go away as Red Gate Software introduces its new SQL Source Control software, which allows T-SQL code to be managed under source control, while working directly from inside of Management Studio. It allows individual developers and development teams to keep their T-SQL code in synch during database development.
SQL Source Control is currently available as part of Red Gate Software’s Early Access Program. The current version works with the free open source Subversion version control system, and the next Early Access Release will support Microsoft Team Foundation Server.
If you would like to get a head start in using SQL Source Control, and would like to provide feedback before its initial release, you can sign up here.
DBA Checklist Updated
I have recently updated and revised my DBA Best Practices Checklist, which is hosted on www.Simple-Talk.com. The goal of the list is not to cover every aspect of SQL Server administration, but to hit the highlights. In addition, not every item in the checklist will apply to every SQL Server instance, under every circumstance. So like any list of SQL Server best practices, don’t forget that they may or may not apply to your environment.
If you would like to add your own items to the checklist, or to provide other feedback on the checklist, please do so here, and I will try to include your feedback the next time I update the list.
SQL Server 2008 R2 to be Available in May
This past Tuesday, Microsoft officially announced that SQL Server 2008 R2 will be available in May 2010. See the announcement here.
If you haven’t downloaded the latest CTP yet, you still can here.
Speaking at European PASS
I just heard that two of my presentations have been accepted for the European PASS Conference 2010 in Neuss, Germany, April 21-23, 2010. My sessions include:
How Do You Handle the Stress of Being a DBA?
This is a reprint of my editorial at SQLServerCentral.com. There is a lively discussion at the SSC forum on this topic, or feel free to comment here.
While being a DBA has many benefits, it can also be a job with many stressful drawbacks. Some of them that come to mind include:
- As the organization’s protector of the data, DBAs often have great responsibility. A careless mistake could potentially cost your organization thousands, if not hundreds of thousands of dollars (and your job).
- Many DBAs don’t work typical 40 hour weeks. Many work weeknights, weekends, and holidays, all without any overtime pay.
- Getting called at home in the middle of the night or on weekends, and often having to come into the office to fix a problem.
- While one crisis at a time is enough for anyone, there are often situations where multiple crises occur at the same time, creating a very hectic environment.
- Getting blamed for problems that are beyond your control, such as the poor performance of a badly-designed, mission-critical application.
- Being told to do one thing by one manager, but then being told to do something different by another manager.
- Being assigned a project without the necessary resources and time to complete it successfully.
- Having developers give you a bad time because you are trying to enforce best practices and to protect the integrity of the organization’s data.
- As a DBA, you often see a bigger picture of how IT works than others, giving you a great perspective on how to make things better, but only to have your ideas for improvements ignored.
- And on and on.
While you may not have experience all of these drawbacks, I am sure you have experienced some of them. So my question to you is: What’s the best way to deal with the inevitable stress of being a DBA? Are you the type of individual who thrives on stress, do you just tough it out, do you take action to reduce stress as much as possible, or do you have other ways of relieving stress? Please share with us how you cope with the stress of being a DBA.