Tribal SQL

I am honored to announce that a chapter I wrote has been published in a book. Nope – it’s not the additional Appendix that I sent the author of Everyone Poops, but is instead Tribal SQL. Edited and produced by the infamous Jen McCown and published by Red Gate the books is on sale now.

If you are attending PASS Summit you can pick up a free copy at the Red Gate booth October 16th 6 – 8PM, and you can meet some of the authors Friday October 18th at 10:45AM.

My chapter carries the title Guerrilla Project Management for DBAs and offers advice on how a DBA can use some simple techniques to better communicate what they do, how effective they are, and why they should be given huge raises.

Here is an excerpt from the book:

A DBA’s Place in the Organization

Organizational skills matter more to a DBA than many other technical jobs due to the diverse nature of their workload. In addition, this diversity exposes the DBA to a greater surface area of the organization than is typical for most technical roles. As part of our jobs, we talk to many people:

  • Vendor’s technical resources – mainly to ask why they need ‘sa’ access, but also to request updated pictures of them that are coincidentally the size of a dartboard
  • Internal development resources – mainly to ask politely why they decided that a homegrown triple-nested cursor implementation of GROUP BY was a good idea, but also to enquire, for no particular reason at all, about their food allergies.
  • Business stakeholders – mainly to discuss capacity-planning decisions, but also to find out how to prevent an in-ear Bluetooth headset from affecting one’s golf swing.
  • Internal semi-technical resources (project managers, product managers, business analysts) – mainly to help with decisions about performance, capacity, and future goals for each product that needs database resources, but also to spread misinformation (“What, you didn’t know that using the first column in Excel has been outlawed as part of the Patriot Act?”)
  • Internal IT resources – mainly to work with them in configuring and securing the hardware and software platforms on which the DBMS infrastructure depends, but also to trade Magic: The Gathering playing cards
  • Management resources – to complain about all the above people

Since we talk to so many people, we are at higher risk of finding ourselves in the cross hairs of the blame gun.

Reasons you should buy this book:

  1. All author royalties go the the worthy charity Computers 4 Africa.
  2. There are many other great chapters from my fellow authors including:
    • What changed? Auditing solutions in SQL Server
    • Agile Database Development
    • Verifying backups using statistical sampling
    • Taming Transactional Replication
    • SQL Injection: How it Works and How to Thwart it
    • Building Better Reports

Hit it up Tribal SQL on Amazon to purchase: