For the day-to-day DBA, there are dangers around every corner; monsters waiting to strike down the unsuspecting database with a resource-hungry query, an inefficient data load, or even outright data corruption. When the worst happens, and SQL Server is down, or performance is suffering, customers are quick to complain. During such difficult periods, you, the DBA, are the centre of attention. Suddenly, three or four people crowd your desk, laser beam focused on your every action, fully expecting you to solve the problem quickly. The success of your career as a DBA depends largely on how well-prepared you are to deal with such situations. Without verified backups, sound server documentation, and a ready supply of tried-and tested troubleshooting tools, there is no safe place to hide when the monster rears up. All you can do is buy some time, patch things up as best you can and then duck away into your cubicle, which, if you lost any data in the process, may soon be empty. However, with the tools and techniques provided in the SQL Server Tacklebox, you will be fully-equipped to fight back. Inside, you'll find scripts that will allow you to automate and standardize SQL Server installation, document and report on your servers, migrate data and manage data growth, troubleshoot performance issues, receive notifications of impending danger, secure access to your servers and fight off data corruption. In short, you'll be able to respond quickly and professionally to the many issues that blight the waking, and often sleeping, hours of the DBA. Then, one day, who knows? That cubicle may turn into an executive office with wall-to-wall tinted windows revealing a flowing brook outside, where no monsters live.
I have read a lot of SQL books by now, so a lot of what I get from them is just picking up on little things. For example, I did my first command line install because of the SQL Server Tacklebox and would recommend that to my team going forward. Also, I had heard of items like sp_foreachdb and tabledifference, but getting reminded of them will make me more likely to use them.
The idea of storing information relating to all of your databases in a central location is certainly not new, but Rodney does a pretty good job of showing how easy it is that this can be accomplished. The scripts and SSIS packages provided will lay the foundation for any new DBA in this endeavor. And, even if you aren't planning on implementing the central repository, these scripts will help to understand the important topics being addressed. All in all a very easy read.
I found this little book more useful than other complex books. It contains practical scripts for administering SQL Server installation, and is an easy reading.