More DBA job interview questions and answers at
http://dba.fyicenter.com/Interview-Questions/
(Continued from previous question...)
WHAT EXACTLY IS A DBA? - Application DBA
Application DBA
In direct contrast to the system DBA is the application DBA. The application DBA focuses on database design and the ongoing support and administration of databases for a specific application or applications. The application DBA is likely to be an expert at writing and debugging complex SQL and understands the best ways to incorporate database requests into application programs. The application DBA must also be capable of performing database change management, performance tuning, and most of the other roles of the DBA. The difference is the focus of the application DBA—it is on a specific subset of applications rather than the overall DBMS implementation and database environment.
Not every organization staffs application DBAs. However, when application DBAs exist, general-purpose DBAs are still required to support the overall database environment and infrastructure. When application DBAs do not exist within an organization, general-purpose DBAs are likely to be assigned to support specific applications while also maintaining the organization's database environment.
There are pros and cons to staffing application DBAs. The arguments in favor of application DBAs include the following:
*
An application DBA can better focus on an individual application, which can result in better service to the developers of that application.
*
The application DBA is more often viewed as an integral component of the development team and therefore is better informed about new development plans and changes.
*
Because the application DBA works consistently on a specific set of applications, he can acquire a better overall understanding of how each application works, enabling him to better support the needs of the application developers.
*
With a more comprehensive understanding of the application, an application DBA will have a better understanding of how the application impacts the overall business. This knowledge will likely result in the execution of DBA tasks to better support the organization.
But all is not favorable for application DBAs. There are cons to implementing an application DBA role:
*
An application DBA can lose sight of the overall data needs of the organization because of his narrow focus on a single application.
*
The application DBA can become isolated. Lack of communication with a centralized DBA group (if one exists) can result in diminished sharing of skills.
*
When an application DBA implements useful procedures, it takes more effort to share these procedures with the other DBAs.
*
Due to the application-centric nature of the position, an application DBA can lose sight of new features and functionality delivered by the DBMS group.
In general, when staffing application DBAs, be sure to also staff a centralized DBA group. The application DBAs should have primary responsibility for specific applications, but should also be viewed as part of the centralized DBA group.
(Continued on next question...)
