Episodes / Episode 1 of 9
SQL Server DBA Orientation: Your First Day on the Job
Your first day as a SQL Server DBA. Nobody tells you what your job is; they tell you what’s broken. Before you start fixing, figure out who does what, who you work for, and who works for you.
Watch on YouTubeFull course playlistSubscribe
In this episode
- The five IT roles that get mixed up (DBA, database architect, sysadmin, domain admin, network admin) and where your job stops
- Rule out the database first, then say so clearly when it’s not the database
- Onboarding: find the apps that make a bunch of money or make people scream, and the SQL Servers behind them
- Who can task you, who you can task, and how to get it in writing
- How your team communicates and documents, and how to get your feet wet
Chapters
Transcript
Read the full transcript
Welcome to your first day as a DBA. Nobody is going to sit you down and tell you what your job is. They’re going to tell you what’s broken. So before you start fixing, let’s figure out who does what, who you work for, and who works for you.
What is your role?
Five jobs get mixed up in every IT shop. Learn where yours stops.
That’s you. You keep the databases alive, backed up, fast, and secure. When the database is down, it’s your fault. When the database is slow, it’s your fault. When the network is down, people will still call you first, because the app says “cannot connect to database.”
The architect decides how the data is shaped: the tables, the keys, how the app talks to the database. The architect drew the house. The DBA keeps the house standing. There is a good chance you will end up being both the DBA and the architect.
The sysadmin owns the Windows server underneath SQL Server: the operating system, the patches, the CPU, the RAM, and the disks. SQL Server lives in their house. You’re a tenant. A nice tenant, who brings cookies when you need more RAM.
The domain admin owns Active Directory: the user accounts, the groups, and the service accounts. If you need a login created, or someone added to a group, ask the domain admin. Many shops also have an identity management team that handles the simpler, keep-the-lights-on tasks.
The network admin owns the pipes: firewalls, routing, and everything between the app server and your SQL Server. Bigger shops are splitting this job up: one team for firewalls, one team for routers, and one team for load balancers. When the app can’t reach the database, it’s usually the network. They’ll tell you it’s the database first. That’s fine. It’s tradition.
So when the database gets blamed, do your due diligence. Rule out the database first. Then say so clearly, and explain how you came to that conclusion.
Some of you work at a shop where you’re all five of these people. Congratulations. You’re a sysadmin with a SQL hobby, and episode 9 is for you.
Onboarding
On day one, where do you start looking? Start with the most important applications. You’re looking for the apps that make a bunch of money, or make a lot of people scream when they stop working. Those are the ones you protect first.
What are the SQL Servers that support them? Write them down. Server name, instance name, which app. You’ll build on this list in episode 4. How do I access them? Don’t just ask. Test it. More on that in a minute.
Find out who’s allowed to put work on your plate, and how they do it.
Support. They’ll bring you what customers are yelling about. Developers. They’ll bring you releases, requests, and “quick questions” that take three days.
If the answer is “anybody who knows your name on Teams,” you’re going to have a bad time. Or on Slack. Many shops are switching from Teams to Slack, or using both. Get it in writing: who can task you, and through what system.
Now, what teams can you task? This list is just as important, because a DBA can’t do much alone.
Who makes Active Directory changes for me? Who can modify servers for me? Adding CPU, adding RAM, adding storage. Ask how long each one takes, right now, while nothing is on fire. If adding a disk takes two weeks of paperwork, you need to know that before the disk is 99% full, not after.
Who makes networking changes for me? Opening firewall ports, and handling routing.
Get names, not team names. “The network team” doesn’t answer the phone at 2:00 AM. Dave does. And to the other teams, you might be Dave.
So learn who manages each team, and who’s on it. Build a relationship with those people before you need them. And document each team’s on-call process: who’s on call, and how to reach them.
The ticketing system is for work. The bug tracking system is for things the developers broke. The change tracking system is for anything you change in production. If it isn’t in change tracking, it wasn’t approved. If it wasn’t approved, it’s your fault. Email, chat, and Slack are for conversation, not for tasking new work.
When somebody asks you to do something in chat, ask them to put it in a ticket. Not because you’re lazy. Because six months from now, when somebody asks why you dropped that table, “Brad said so on Teams” is not a defense.
Find out where each kind of documentation is kept.
Developers document their apps. Vendor documentation, for the stuff you bought. TTPs: tactics, techniques, and procedures. Policy. Read these first. These are the ones you get fired for. KBs: the knowledge base system.
If half of these don’t exist, that’s normal. Episode 8 covers how to fix it. For now, just know where things are.
Get all your necessary accounts created. Make sure you have a password manager or passkeys, because there will be a lot of accounts. Get added to the correct groups. Test access to the servers. All of them. Log in to every production SQL Server on your list in your first week, on a calm Tuesday afternoon. You do not want to find out your account was never added to the right group at 2:00 AM, during an outage, while your boss is on the bridge call asking why you’re not in yet.
Your first month isn’t for fixing things. It’s for learning who, what, and where. The fixing starts in the next episode. Spoiler: most of the time, the right fix is to do nothing.
