A qualified DBA should be aware of

for a qualified DBA (database Administrator, DB Administrator), it is not sufficient to understand the SQL statements in light. DBAs typically work at the intersection of databases, servers, operators, and developers, so a qualified DBA needs to understand every aspect of it, and can have the ability to debug performance, hardware, and software problems. This article will cover 10 things a beginner DBA needs to know, and see if you already have these capabilities. (Recommended for the Silicon Valley Oracle Video tutorial )

650) this.width=650; "src=" http://183.61.143.148/group1/M00/02/83/tz2PlFRhyEHCEpDKAAGJuzDyh2E630.jpg "/>

Backup and Recovery:

any veritable DBA should know how to use the built-in tools of the DBMS (database management system) to back up and recover data, such as Oracle Recovery Manager and SQL Server Management Studio. In addition, it is also necessary to know which third-party database backup tools are available. You'll find out later that these tools have advantages. In fact, simply backing up a database file does not mean that the backup is a "good" backup.
Basic Optimizations:
When you create an index, the DBA needs to know how to make the tuning recommendations. You need to know some basic indexing strategies, and also know the answers to these questions. For example, when to introduce a clustered index (Clustered)? When to use an overlay index (Covered index)? How does the database optimizer work? Does it depend on the statistics of special tables? How do I update this data? What does using the optimizer mean for reorganizing tables and indexes? How should they be reorganized, and whether they can automate the process?
Assist software Developers:
software developers can build or destroy your database. It is important to help them write efficient query code. You have to help them understand that it is much more efficient to launch 1 query requests at a time than to initiate 1000 requests at a time: in the case of big data, 1 queries return 1000 rows of results that are much faster than the 1000 queries each time. As a DBA, help them understand that sometimes it is better to perform operations in a DBMS than in code. A typical case is that crawling large amounts of data over the network and merging locally is likely to be slower than a direct aggregate function (Aggregate functions) query.
Storage System:
The performance bottleneck for most databases is on disk, and it is important to know where your database is located and how the DBMS accesses the physical data. If your business has storage teams, contact them and master some of the important performance metrics that they are monitoring for storage, such as IOPS and response times.

Understanding query Plans:

A primary DBA should know how to generate and read basic query plans. It does not necessarily require you to fully understand all of the content, but a few key processes are still to be mastered, such as random full table scans and nested loops (Nested Loops) may cause problems. Again, you need to know when the optimizer will recommend changes, why such changes will take effect, and how these actions will compromise the performance of the system.

Understanding Normalization:
A normalized database table (normalized Tables) is the foundation of a well-designed relational database, but sometimes it can also bring disaster. DBAs need to understand and know how to incorporate data into the first, second, and third paradigms. Why is normalization important and when is it likely to be a negative factor? Know the difference between a primary key, a foreign key, and a unique key, and know how to force a pair of one or one-to-many relationships.
Understanding the SQL language:
DBAs also need to master SQL DML (Data Manipulation language) and DDL (data definition Language). DML contains items such as select (query), UPDATE, insert (insert), and delete (delete). The DDL contains the CREATE table (creating tables) and ALTER TABLE (delete table). The primary DBA should understand how to create and modify tables and indexes, and know the difference between deleting records, truncating tables, and discarding tables. Of course, you can't forget the view.
Operating System:
DBAs also need to be familiar with the operating system and know the differences between different operating systems, such as security settings, integration with Active Directory, LDAP, and naming conventions. You also need to know how the database is started, what scripts are required to start, shut down, or temporarily lock the user's access.
Script:
to make the job more efficient, scripting is essential. Imagine that you have 10 or more databases that need to be managed, can you only log in individually and start/stop them manually? Go find this Scripting Guide to see how to do this in bulk.
stored procedures and triggers:
a separate list of stored procedures and triggers is due to the fact that this is more like programming than a "composite" SQL statement. Anyway, you need to know when to use them and let the development team know the benefits of not doing it in code. Similarly, many third-party applications bring their own stored procedures and triggers as needed. Being able to read these processes and understand their logic is helpful in troubleshooting future performance problems. The faster you can understand these processes, the more comfortable you can be with the databases you manage.

Learn More Programming Language Tutorials can login e mentor network.

A qualified DBA should be aware of