Subscribe to SQL Server Magazine | See More SQL Server and Database Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
back to blog index

The root of this blog post is witnessing one too many DBAs, either through direct action or indirectly by failing to act, damage or destroy the very databases they are charged with protecting.  In a sense, DBAs are the guardians of an extremely valuable corporate asset - its data.  But a large number of DBAs, while responsible for databases, have no idea how to be a proactive guardian of that data.  And, in my opinion, that is a moral and ethical breach more than it is a technical shortcoming.  This is even more important when we consider that some of these databases have a direct impact on human lives, particularly medical, security, and defense related data.  (I write more about this topic in my monthly column in Database Trends & Applications Magazine.)

When we consider other professions with a direct effect on human lives, we can see that they have all implemented professional codes of ethics.  Famously, the Hippocratic Oath of doctors is just the beginning.  "First, do no harm."  Professional Engineers (PE), whose buildings might fall down on our heads were they only motivated by maximizing profits, must adhere to seven fundamental canons.  Among them, PE's shall hold paramount the safety, health, and welfare of the public and that PE's shall perform services only in areas of their core competency.  Even professions that affect our finances (e.g., certified public accountants) and contractual obligations (e.g., lawyers) are sworn to uphold professional codes of ethics.

The Association for Computing Machinery has a rather long code of conduct for a variety of computer-related disciplines.  But the closest it gets to a DBA-type role is one for a systems engineer.  Certainly, it has some passages which are reusable, such as those related to conflicts of interest.  Honestly, though, it's not that close.  I think we need our own - a code of ethics for DBAs, database programmers, and BI professionals.

So - what do you think?  What are some ethical standards that we should aspire to?  What are some big ethical lapses that you've witnessed, and that we should be sure to avoid as true professionals?

End of Article



Post Your Comments Here

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now

Reader Comments

This is a valid, but difficult question. Being the sole dba and typically working for people that don't understand the funtion(s) of a dba, I am often directed to make do with little personnel or hardware resources. Security and database maintenance are seen as secondary priorities to providing support for developers and data to customers. The joke here is that I'm risk-adverse, but my thought is that is what I was hired for - to protect the data.

loriedwards

Article Rating 5 out of 5

Just a random thought - Any code should include the words "To the best of my ability,...". That leaves it up to me (and my employer, I would hope) to improve my ability, through training, reading, best practices, whatever.

If something untoward were to happen with the data I was protecting, I would rather be thought of as slightly unknowledgeable than unethical. Knowledge can be learned; I don't think "evil" can be fixed.

marksil

Article Rating 4 out of 5

Interesting but if a hiring company has no interest in the importance of databases, surely the company is at fault for not been aware (ignorance is not a defence)in the importance of database systems and maintenace. At the moment there is no incentive or consequences involved for a lot of companies to ensure best practices are enforced or in the training of there staff.

tullshaun@hotmail.com

Article Rating 3 out of 5

I think that we should strive to find the right solution for the problem in the current environment.

I've been in environments where the staff was so pedantic about "the process" that they lost the spirit behind the need to support the users, and in environments where there was too much other work to do to spend time doing more than the minimum necessary to get the job done. Neither one was good, but the management and staff seemed to think that it was okay for them at the time.

ryanbseattle

Article Rating 3 out of 5

I agree there needs to be a code of ethics for a Database Administrator. I also think the responsibilities for a Database Administrator need to be more clearly defined. I have worked with databases in some form or antoher for over 12 years and I find that most companies have no idea what a Database Administrators job should be. I have worked at my current position for 8 years and I find that many times ethics and best practices go out the door in exchange for profit and customer satisfaction. I continue to explain the need for data protection and best practices. Sometimes I feel between a rock and a hard place. Hopefully in the future as the need for instant data, reports, and metrics grows corporations will begin to value their DBA's more and listen to them.

Teresa Mills

Article Rating 4 out of 5

 



1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30      
or
More blogs about technology, databases, and SQL Server.
 

ADS BY GOOGLE