Seven habits of a high efficiency DBA

1. Professional versatile (being an expert generalist)

Knowledge of the storage, operating system and other fields, Cross-platform database technology is also necessary to master, You can't leave the Windows environment. Nothing can be done under UNIX. It may seem a bit demanding, but the individual believes that through continuous learning and a good accumulation of knowledge will allow you to be infinitely close to this ability.

2. Understand the needs of business and users (understand the business and user expectations).

How to apply the knowledge of the database to the business needs, not to the user a "carpenter carrying a hammer, see what is nails" feeling is needed a little art.

3. Build more formal service-level agreements through quantifiable metrics (

Build more granular service level agreements (SLAs) via quantitative and Easy-to-understand metrics)

If the user (or your boss) is satisfied with your database management work, there is always a place to agree, which should come from the service level agreement. Service-level agreements are one of the easiest places for many DBAs to overlook.

4. Partition the environment into smaller, more manageable components (break down the environment into smaller, manageable pieces)

A package plan is not a good idea, divide and conquer. This is also easy to agree with the client.

5. Focus on the task rather than the details of the implementation (be task-focused, not necessarily on how to accomplish it)

This should be in relation to the developer. Instead of focusing too much on the details of programming, DBAs should focus on the task-effectively interacting with the database. (This may seem a bit grudging, but it's easy to understand from an efficient DBA's point of view, huh)

6. Isolate and delegate common tasks (segregate and delegate the mundane).

If from a technical leader's point of view, this is necessary. Since it's an efficient DBA, there's no need to be hands-on about trivial things.

7. Eliminate those gadgets that can be used in certain environments (Weed out the One-trick ponies)

Specific Third-party tools, GUI tools, etc. only make the environment more complex. An efficient DBA should be committed to simplifying and standardizing the entire environment.

The DBA, in fact, is quite suitable for other types of work.

From Excellence to excellence, or from ordinary to mediocre, this is a problem.