How I Became A.txt

In college, I took a single database course. I'd messed around with Microsoft Access a bit, but wanted to get a better handle on what I was doing. The course was not at all what I was expecting. I passed and did OK, but I didn't completely grasp the material. The class was mostly deep RDBMS theory including "how do we store this on disk" - I wrote minimal amounts of SQL in this course because it wasn't required.

I graduated and took my shiny new Computer Science diploma to my first job. At the time, I hadn't so much as looked at Microsoft Windows in six months - a fact that I wore like a badge of honor for a while. This was in an era when Microsoft had a pretty bad reputation in the software world and as was typical for CompSci students in the late 90s, I wasn't much of a fan. But hey, a job's a job and within a few months I had a solid handle on Classic ASP, building apps with it and handling some of the server admin stuff on the NT4 boxes that hosted them. I spent a little over 5 years there and got minimal exposure to databases as that wasn't what my job function demanded - I'd write some queries against DB2 on the mainframe or a SQL Server instance, but that was about it. The DBAs took care of everything else.

After a few years, I moved on from that position as I wanted to relocate for personal reasons. I found a job doing some Java work on an in-house application and system customization/integration for an purchased application that was used as the hub for the company's core business. In the course of working on those systems, I started doing a lot more SQL work, but at the time I only knew enough to be really dangerous.

During a project to upgrade that system, I got a crash course in writing good SQL from Allen White, and learned much more about how SQL Server works from both him and Kenal Van Dyke. Allen and Kendal also introduced me to the SQL Server community and my eyes were opened. This was huge.

Over the next several years, I discovered that I was a developer who had DBA tendencies that I just hadn't realized yet. I started to get involved with the SQL Server community. Talked to so many people. Subscribed to dozens of blogs. Attended SQL Saturdays and PASS Summits.

Then, one evening after we finished unpacking equipment and supplies from one of our Rochester SQL Saturdays, Matt Slocum (b|t) just asked me, point-blank. "So do you wanna be a DBA or what?" Ding! The lightbulb flicked on. I'm already doing a whole bunch of this stuff, and enjoying it - why not go for it?

I refocused my efforts on really understanding how SQL Server works. Looked for ways to leverage my programming experience with a slant toward managing databases. Did a lot more non-production DBA type work (I didn't a lot of access to production, which was probably a good thing). After searching for quite a while, I landed a position as a full-time production DBA with a company operating a SaaS platform. It was a bit of a leap but one that I had to take as it was the right thing that came along at the right time. I'm nearly 2 months in now and I've learned a ton already. Made a few slip-ups, but that's to be expected - just have to learn from that and move forward.