|
As a freelancer I work with SMEs who usually have no tech experience / ability. They need a system to help their business; I deliver it. I tell them there's a database there, which one, and often (always?) send them some documentation so if I die whoever takes over will have a starting point; but beyond that the client has no clue how "the system" actually works, including anything to do with the d/b. I don't deliberately hide anything away from them, but both they and I know that they'd be totally clueless in any case.
|
|
|
|
|
Each Sprint a different developer gets the responsibility of doing any schema changes that need to happen. This Sprint it's me.
I get to use PowerDesigner 7.5 and the pdm file gets read by some arcane process that does way more crap than it needs to.
|
|
|
|
|
MarkTJohnson wrote: Each Sprint a different developer gets the responsibility of doing any schema changes that need to happen. That's the development-part; what about production? Who does the backups, and who gets blamed if the restore fails?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
It's obvious the database owner is the nerd who lives in the server room.
|
|
|
|
|
Data is owned by who ever put it there and manages.
Database + Server is DB Admin.
DB Admin will seek to make sure you can access what you need (not want), that security set up correctly, that bad queries looked into.
Whom ever puts bad data in, is their fault.
|
|
|
|
|
We sold it to the Illuminati
veni bibi saltavi
|
|
|
|
|
Actually, we only leased it - not much trade in value for used databases any more with all the hacking.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
The owner delegates the responsibility to some people or companies. Those who are responsible for maintenance do not own the database, nor the data. The role of dba is currently part of the network-guys.
Some of it is local and under control, some of it is cloudy.
The stablemaster may claim it is his horse, but can't sell the animal. It's also not the stablemaster who pays for the food from his coinage.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Probably someone else, though
|
|
|
|
|
Nemanja Trifunovic wrote: Probably Luckily someone else, though FTFY
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
'Not sure, policy prevents the sharing of that knowledge'
I wish it was more of a joke.
|
|
|
|
|
I feel your pain
|
|
|
|
|
works great.
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
|
|
|
|
|
I remember those days. Days when we had a dev environment, a UAT environment, a training environment (complete with document folders, interfaces, mainframe instances).
|
|
|
|
|
In that time, we still had an ashtray next to the keyboard. People would knock before entering.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Not quite!
Actually, less than 10 years ago … but we were all old-school and luckily so were the holders of the purse strings
|
|
|
|