The DBA Code of Ethics

• zach_john

  SSCertifiable

  Points: 5922

  More actions

  January 29, 2004 at 9:43 am

  #492193

  Always an admirer of your work Steve, but you have way too much time on your hands. If you have some free time I have some servers that can use your expertise.

  Dying at The AP

  Zach

  ps. just joshing you.

   

   

  
  John Zacharkan

• James Luetkehoelter

  SSCommitted

  Points: 1733

  More actions

  January 30, 2004 at 11:53 am

  #492387

  I love this article Steve.  These are the kinds of things I like to think about and discuss.

  At one point I was preaching a DBA ten commandments.  One that I included was "Thou shalt know thy data" -- meaning, it isn't enough just to maintain integrity, security, and availability, but also to have a detailed understanding of what the data is.  Not just from a modeling perspective, but from an actual content and usage perspective.

  That point was often argued -- what does everyone think?

• David.Poole

  SSC Guru

  Points: 76035

  More actions

  February 2, 2004 at 1:55 am

  #492452

  "Thous shalt know thy data"

  Good up to a point, however some databases contains thousands of tables.

  I think that a good general rule for all IT personnel (and in particular DBA's) is to learn about the business of the company that employs you.

  I've worked with people who have become really high flyers and they have all put particular effort into

  • Learning the business over and above their discipline.
  • Socialising with other employees outside of their department.  IT is a fantastic discipline for getting to meet people.
  • Putting Joe in sales in touch with Mike in production thus solving problems for both of them.
  • Getting a name for being a good listener.

  LinkedIn Profile

• mdonahue 65611

  Grasshopper

  Points: 13

  More actions

  July 7, 2010 at 2:27 pm

  #1189852

  Steve, not sure where this can relate in but how would you address the issue of data deletion from a DBA perspective?

  In the aspect of a Database containing legal information on criminals...

  i.e.

  1. User enters in data on a person that was incorrect, i.e. totally wrong or for a different person. This should be removed?

  a. Enter in a DOB that was from another person, this should be removed as the history woudl reflect this person used an "alias" DOB and would be incorrect as the person did not provide this information.

  b. User selects the incorrect person and books them into jail in the system. This should be deleted as the person should not have another booking on their record that was not theirs.

  2. User enters in something erroneous, but on the correct person, this should be corrected with a clarification entry?

  a. User enters in one thing and meant another. Entry should be "edited" by user and a clarification entry made so that the correct information is saved as the current value, yet the history is retained.

  b. User enters in something that flows via an interface to another legal system. As far as I am concerned, when this data leaves our system and flows to the other department and was on the right person, if it was in error the other system should reject it.

  Thoughts? Thanks