A detailed explanation of what a DBA

Database administrator, in English, is DB Administrator, referred to as DBA. This position means a different meaning to different people. A small software development studio is more broadly responsible than a large company with a highly detailed division of labor. A company, whether it is developing its own application software or buying third-party applications, as long as it involves a database (how many applications that do not involve the database?) Database is the soul and the brain of business, you need to decide whether to hire one or several DBAs. Knowing what the DBA's requirements are, the definition of this position within the enterprise or the future DBA will be critical.

Some of the responsibilities of the DBA:

Install and upgrade database servers (such as Oracle, Microsoft SQL Server), and application tools.
The database designs system storage scenarios and develops future storage requirements plans.
Once a developer has designed an application, the DBA is required to create the database storage structure (tablespaces).
Once a developer has designed an application, the DBA is required to create the database object (tables,views,indexes).
Modify the structure of the database, if necessary, based on feedback from the developer.
The user who enlists the database, maintains the security of the database.
Ensure that the database is used in compliance with intellectual property laws.
Control and monitor user access to the database.
Monitor and optimize the performance of your database.
Develop a database backup plan to recover database information when a disaster occurs
Maintain archiving or backup data on the appropriate media
Backing up and recovering databases
Contact the manufacturer of the database system to track technical information.

The personality characteristics of a DBA

Most of the time managers overlook the DBA's personality, and they focus only on the technical capabilities of the DBA. In fact, each of the responsibilities mentioned above means that DBAs need to deal with a variety of people who may be sellers, users, developers, or managers. This means: DBAs must have the following personality traits:

Confidence
Curiosity
Tough willpower.
Sophisticated
Self-driven
Attention to detail

Why are these personality traits important?

I had a few men who lacked confidence, and they asked me a few questions, and they didn't have the confidence to make the smallest decision. They also lack the initiative to work. This may not be a big problem for junior DBAs, but for senior DBAs, if they lack confidence, who can they rely on to help them make decisions? In a DBA interview, even if you can't answer a technical question, you have to show enough confidence. The most deadly thing is not knowing the answer, but not knowing where to get the answer.

Almost all database systems are constantly being updated. However, not all updates have technical documentation. For a good dba, Curiosity is necessary. DBAs who have no curiosity and thirst for knowledge are always waiting for someone to tell them the answer. An inquisitive DBA will install the latest version of the database system and immediately start searching for even the smallest of features and performance differences and enhancements to improve their work. One question that must be asked is: What references do you have on hand? How do you use them? Without a doubt, if you answer only the database documents, or you haven't even read them, your "stock market value" will be greatly reduced. Curiosity drives DBAs to understand data Dictionary, management tools (tools), or other support packages (Packages).

DBAs often run into tricky problems. Finding the answer is a personality trait that requires tough willpower and can withstand beating. I often see questions from DBAs on some discussion groups or forums, which are often questions that the questioner himself can solve if they have tough personality traits and try to find the answer to the question.

Self-drive is important for everyone, especially for DBAs. DBAs should be able to find ways to make problems happen, rather than wait for the problem to occur. Self-driven DBAs often try to get or write the necessary scripts themselves to monitor items including data table size (table size), tablespace usage (tablespace usage), and they will be in trouble if they are overlooked. When you're on the test, DBAs are often asked about the experience of PL/SQL or sql*plus, which separates you from the DBAs who have never written the scripts you need.

Needless to say, users, who are dealing with programmers and managers, need to be sophisticated enough. A DBA who does not work for you will not do anything good for you, only ignite the flames of hostility in your department. Tact is such a ability, you advise someone to go to the underworld, haha, finally this person with longing mood went. Many times, developers, managers, users, they will make unreasonable demands, DBAs need to skillfully guide, revise their requirements, persuade them. When you are in the exam, your response will be a good indication of your sophistication.

This article is from "Ghost" blog, be sure to keep this source http://caizi.blog.51cto.com/5234706/1535205