Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

Re: (OT) Old blood versus new blood

by dws (Chancellor)
on Dec 18, 2001 at 02:45 UTC ( #132708=note: print w/replies, xml ) Need Help??

in reply to (OT) Old blood versus new blood

Now, I can't say that I am much of a database expert, but this guy clearly knew his stuff. Then I asked him about normalization ...

As mentioned, the problem with the label "DBA" is the definition of the DBA role depends a lot on the organizational context. I don't think that it's entirely reasonable to take the position that every DBA should know the details of normalization. That depends on where you draw a line.

I've worked in shops where the DBA worked in Operations, but the developer doing schema design worked in R&D. The DBA worried about the physical upkeep of the system, while the developer worried about conceptual integrity. I've also worked in shops where "DBA" meant "everything to do with that icky database thing, which nobody else wants to touch for fear of their mortal soul." The trick is to be clear about where you're drawing the line between logical and physical design.

In chatting with our CTO, he tells me that this is something that he has seen this quite a bit in older DBAs. He claims that they worked in a time when space and CPU time were at a premium and therefore they didn't focus as much on "esoteric" concepts such as normalization.

This generalizes past the DBA. A lot of people get stuck in whatever was hot when they first learned. And some of the people who manage to move past that still fall back on what once was when they're under pressure. And some people have been around through enough fad cycles to realize that what's hot today probably won't be in a few years. That's one of the benefits of experience.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://132708]
[marto]: they still don't know there was a problem, nobody told them! :P
[Corion]: marto: Ow! I would assume there is a cron job monitoring the free disk space and automatically opening a ticket at 90%, 95% and 100% usage...
[Corion]: Even we had automatic emails back when we maintained the machine ourselves...
[marto]: Corion you under estimate how lazy these admins are :P
[Discipulus]: we too; using opsview alarms
[marto]: the key word: outsourcing ;)
[Corion]: marto: Yeah, feels like that ;) You could set up the cronjob that auto-creates tickets :-))
[marto]: the ticketing system does not accept calls via email, nor has it a working API. It's tied into Active Directory for authentication and the Solaris boxes aren't on that domain
[Corion]: The one thing I haven't figured out a solution to is how to get an edge-trigger instead of sending an email every 5 minutes if the usage is above 90%. I want one mail when it goes over 90% but no more emails as long as it stays between 90% and 95%.
[Corion]: marto: Clever! ;)

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (9)
As of 2017-01-24 10:08 GMT
Find Nodes?
    Voting Booth?
    Do you watch meteor showers?

    Results (203 votes). Check out past polls.