Re: how much theory should a DBA learn?

"Ryan Gaffuri" <rgaffuri_at_cox.net> wrote in message news:1efdad5b.0310091818.5c755821_at_posting.google.com...
> I specialize in Oracle. I know a little relational theory. How
> important is it to learn more?

That totally depends how ambitious your goals are. Is constant learning your guiding principle?

> Where can I find good sources on
> research into new types of databases, etc... that is non-vendor
> specific?

There is also studying theory vs. learning oracle dilemma. Too many practitioners take vendor's implementation as a gospel, so you are on the right track here.

Note, then when progressing in your studying you would become less and less interested in DBA job. Although DBA needs to have some analytical skills for performance tuning, for example, his routine are mechanical tasks of backup, maintenance, and other boring stuff, that would be automated in a decade or so. Therefore, if I were DBA, I wouldn't feel myself secure in a long term.

As far as books are concerned, studying Date's Introduction is a good push into the field. If you become interested in a particular subject, then Date's bibliography notes is also a good start.

Be careful not to jump to Abiteboul&Hull&Vianu Alice book and citeseer papers too soon, as the bar there is significantly higher. Among the papers, reviews are almost always enjoyable to read (with the rare exceptioins like Graafe optimization) and they wiould funel your enthusiasm. Received on Fri Oct 10 2003 - 12:13:17 CDT