Fish in too much water.

[samwize.livejournal.com]

I've been working application support/DBA-guy for this company for about a month now. It's a small shop that provides tech support for another company's big-ass software suite. I've spent most of my career as a Windows Server Guy (MCSE, MCDBA, MC Chis kicks butt, etc) and have discovered that I know far, far, FAR more about windows networking et al than anyone else in the company. We don't have an IT department. Problems just "get fixed" by whoever is around. No one here knows how our network is configured. There is no documentation. Our "server room" is a joke. Today, after I spotted, diagnosed, and repaired YET ANOTHER severe error on our core servers, I asked the seniormost guy here:

"So, who exactly _is_ our System Administrator, anyways? One of the VPs?"

"Uh... You. Pretty much. You are, now."

"Oh....Huh....Guess it's a good thing I scammed myself some domain admin privs, then, huh?"

"Uh...yeah."

I feel like... Hercules on American Gladiators.

Comments

[inahandbasket]

sounds like you're on solid ground to demand a raise... ^_^

[gilmoure.livejournal.com]

Money makes the fishy swim faster.

[crazdgamer.livejournal.com]

Congrats on the "promotion"!

Now you have to figure out who you report to regarding network-wide system issues. Luckily you're in a small shop, otherwise finding your place on an organizational chart could be disasterous.

"Ummm... how come there's no one below me and 18 people directly above me?"

[jon787.livejournal.com]

Because you are holding the chart upside down sir.

[the-s-guy.livejournal.com]

Just tell any manager who asks that you report to someone else :)

But yes. Now that you have the Mark of the Sysadmin, you're DOOOOOOOMED.

[fiannnachruinne.livejournal.com]

Definitely need to ask for a raise. And sell them on the idea of letting you go through and rebuild and document the network. Before or after you ask for a raise, your choice.