Database administration is a very technical discipline, but
it is also a discipline in which the practitioner is very visible politically
within the organization. DBAs should be armed with a proper attitude and
sufficient technical knowledge before attempting to practice database
administration. This blog entry, and the next few, will discuss some basic
rules of thumb for DBAs to follow to make their job easier to deal with.
Number 1: Write Down Everything
During the course of performing your job as a DBA you are likely to
encounter many challenging tasks and time-consuming problems. Be sure to
document the processes you use to resolve problems and overcome challenges.
Such documentation can be very valuable should you encounter the same, or a
similar, problem in the future. It is better to read your notes than to try to
re-create a scenario from memory.
A corollary of this rule of thumb is to “keep everything.” Most good DBA's
are also pack rats. DBA is just the job for you if you are a pack rat. It is a
good practice to store away everything you come across during the course of
performing your job. This includes, but is not limited to:
- Manuals – old and new; online and printed
- Links - to useful web sites with database information (but you might
consider printing off some of your favorite web links because sometimes links
go dead)
- Scripts – to make changes, run reorgs, whatever
- Programs – quick fix programs, sample programs, etc.
- Proceedings and Presentations – from user groups and conferences
- CDs – containing demos, products, white papers, presentations, manuals,
etc.
- Notes – from design review meetings, specification meetings, team
meetings, user groups and conferences, etc.
- Course Books – from any classes you have attended
- Books – for all of your DBMSs and tools
- White Papers – on your DBMS and related products and issues
- Reports – from performance monitors, queries, applications, etc.
- Articles – from magazines (or web sites)
Of course, keeping all of that information organized and accessible can be a
Herculean challenge. Maybe it should all be kept in a database? Hmmm...
In the next couple of weeks I will post additional "rules of
thumb" for DBAs. If you have a favorite, be sure to log in and contribute
your ideas using the "Add Comment" area below...