Industry


Ads by TechWords

See your link here


Sharky's picture
Sharky

Shark Tank

Oh, THAT one!

Network admin -- let's call him Fred Smith -- sends an e-mail to his group's applications admin, database admin, developer and interim IT manager, reports a pilot fish on the scene.

"He said that there was a database created on the main C: drive of a production server," fish says. "He explained that this is a very dangerous practice, because the database could fill and cause the server to crash."

App admin, DBA and developer all promptly reply, each saying he didn't create the database and doesn't know who might have.

But the net admin is quick with his reply, and adamant -- it's crucial to find out how the database was created, so it doesn't happen again.

After a short pause, app admin replies again: "Just checked the properties of that database. The owner is fsmith."

Reports fish, "We never heard another peep from the network admin the rest of that day."

Sharky wants to hear from you. Send me your true tale of IT life at sharky@computerworld.com. You'll snag a snazzy Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.

Now you can post your own stories of IT ridiculousness at Shark Bait. Join today and vent your IT frustrations to people who've been there, done that.

What People Are Saying

for a while there, i thought it was me

...half of my titles up there. i also do exchange, AV management, wsus, technical support, night guard and janitorial duties.

Always check the safety before pulling the trigger

Why didn't the Network admin check the properties before firing off the email? And why is he creating databases? Isn't that what the DBAs do?

Note the article stated issue was on the C:\ drive...

Obviously, this couldn't have been a real database, especially when created by Network admin. Most likely it was an Excel spreadsheet with "searchable" data.

CAPTCHA: Dover untangle-what Ben did afterward?

Yep.

I hate when that happens / I love when that happens
(depending on which side I'm on)

fsmith AKA

JTB

Sounds EXACTLY like something he'd do.

CAPTCHA: royale not -- Prince Charles, at least not yet, anyway

haiku

Production is down
You are responsible now
The blamestorm rolls in

There's been several Blamestorming sessions at my job.

Blamestorming: Sitting around in a group discussing why a deadline was missed or a project failed, and who was responsible.

Seagull Manager: A manager who flies in, makes a lot of noise, excretes over everything and then leaves.

Blamestorming

Oh, yeah. The conversion to a new state government wide accounting system isn't going well "because of the guy who just retired." Who didn't have anything to do with it, unlike the two people hired into accounting specifically for the conversion.

I feel ya

every problem my current project has is always the fault of the guy who left last year. Never mind the fact he didn't work in that area of the project.

Re: "I feel ya"

This phrase should be reserved for use with/for/on Babmbi.

CAPTCHA: sultry Trainer -- Babmbi in leather

Blame game statute of limitations...

It's a well-known business precept that you always blame the previous guy for current problems... but only for six months. Six months is the limit one can blame their predecessor. After that the higher-ups get bored with the story and start asking for new excuses.