Database administrators are much more than just “table jockeys.” Because of our well-rounded expertise, we are often asked to help evaluate third-party business applications, application development tools and database administration and monitoring products. Over the years, I have developed a Product Evaluation Methodology that you may find helpful.
This blog will focus on the most important responsibility we are charged with as DBAs – ensuring that our organization’s databases can be quickly and easily recovered. My intent with most of these blogs is to provide information that you won’t find from other sources. You can find the mechanics of database administration in a multitude of places. But that’s not the only information you need to become successful at protecting your databases against “unforseen and unfortunate circumstances.”
Because of my background in Oracle Education, I am often asked about Oracle training, which classes would be most beneficial and how to prepare for the certification tests. The purpose of this article is to help students better understand Oracle education and the Oracle certification process.
Ever look at a screen’s output and get that puckered feeling in the pit of your stomach? If you have been working in this profession for any amount of time, you know the feeling I’m talking about. The feeling that makes you think you would rather be living in Montana making woodcarvings at a roadside stand than being a DBA. I’ll be taking a somewhat lighthearted look at the perils of our profession and discuss ways to reduce problem occurrences.
The Foot Rule of Thumb
The Foot Rule of Thumb is pretty simple. You need to experiment and create your own rules of thumb. A while back I wrote a series of interview questions for an online magazine. The questions were the basis for a podcast interview with Jonathan Lewis. What impressed me the most about the interview with Jonathan was the amount of time he spent researching how the database worked. He stated that he became an expert by spending time investigating the database’s intricacies and documenting the results.
Setting up a Successful Test System in Oracle
Let’s continue our discussion on the Art of Being a Successful DBA. The intent of this blog is to help administrators design and standardize on a formalized design review process. The goal of the design review process is to identify and address application design, process flow, program logic and SQL statement problems early in the development lifecycle. Identifying these issues early in the development life cycle allows them to be more easily addressed than if they were to be identified during later stages. That last statement bears repeating. Like any other issue you face, no matter what it is (personal, professional, whatever), the sooner you identify it, the easier it is to correct.
Our blog has received a 7.8 out of 10 “Very Good” rating from the editors at Blogged. The Editor reviews are provided by professional editors who evaluate a blog based on: Frequency of Updates, Relevance of Content, Site Design and Writing Style.
I absolutely and firmly believe that Data Administrators are the unsung heroes of the Information Technology profession. This blog will be shorter than most of the upcoming blogs you will see from me. As a writer, I’m not noted for “keeping it brief”. I used to be an Oracle instructor and I like to pack as many facts as I can into these things. After reading a few of my upcoming blogs, you’ll probably agree.
Ever fumble around at 2 AM looking for that SQL statement you wrote a while back? You know, that one special script that will give you just the information you need to solve the problem and go back to bed? I must admit, I have done my fair share of moonlight script hunting. This blog will provide you with a few recommendations on naming convention best practices.