Database Administration: DBMS, Security, and DBA Roles

Introduction

In evaluating the current field of database administration, several areas demand close attention: Database Management Systems (DBMS), Database Administrator (DBA) roles and responsibilities, database design concepts, database performance, and data integrity and availability. Database security is equally essential — as evidenced by the many breaches that occur on a near-daily basis — for any organization to continue operating effectively. The breach at social networking site Twitter is particularly troublesome given that platform's rapid growth and the volume of sensitive information stored on its servers. Additional critical areas include database backup and database recovery. Each of these topics forms the foundation of a DBA's many tasks in supporting an organization.

The intent of this paper is to provide insights into each of these areas from a DBA standpoint, examining them as strategic concerns relative to the value of data within an organization. Critical success factors for the development of effective database management systems (Guynes & Vanecek, 1996) include thorough systems analysis and design, the development of security and fault-tolerance plans, and the development of change management programs to ensure that departments, employees, and external customers can effectively use the systems designed. Database security forms the foundation of DBMS best practices (Jajodia, 1996) and also serves as a precursor to Service-Oriented Architectures (SOA) and the use of DBMS taxonomies for the creation of Web Services based on the XML language protocol (Erickson & Siau, 2008). All of these factors are taken into account throughout the analysis of DBMS operation, optimization, management, security, scalability, and future trends relative to SOAs and Web Services-based designs.

Database Management Systems

The evolution of databases from simple hierarchical structures to enterprise-wide DBMS platforms parallels their growth from being purely focused on IT tasks to being entirely focused on business and strategic processes and objectives. For this transition to occur, databases had to move away from purely hierarchical designs and adopt more relational data structures that treated each data element as a logical — not necessarily physical — element of the database (Greene, 2008). In order for databases to become more aligned with the business needs of companies, the shift from hierarchical to relational and object-based structures began decades ago and continues today. This shift allows databases to support logical table structures, record definitions, and logical connections across multiple databases regardless of their physical location.

Corresponding to the growth of relational databases is the increasing sophistication of data modeling (Geiger, 2009) and the continued development of constraint-based analysis and optimization routines to ensure high-performance queries and related applications (Benedikt, Dong, Libkin, & Wong, 1998). The development of query-based database logic in conjunction with constraint-based engines for database application development is leading to the creation of configurable Web Services (Firat, Wu, & Madnick, 2009).

The variation in data models has progressed rapidly, with the development of multidimensional tables that can pivot data sets to reveal insights not intuitively obvious from looking at the data itself. Multidimensional analysis using constraints and rules-based logic is also being applied to complex business applications, including optimizing supply chains and creating more effective distributed logistics networks (Segev & Zhao, 1994). The ability to define additional data structures through the many languages used for creating, augmenting, and improving database performance — and integrating databases into enterprise applications — is predicated on structuring databases to be more process-centric rather than purely functional in orientation (Post & Kagan, 2001). One of the primary catalysts of this process-centric approach is the widespread adoption of XML as a communications protocol, which has been continually improved in terms of security and scalability (Roth, Hernandez, Coulthard, Yan, et al., 2006). The role of XML is also critically important in the context of creating Web Services that rely on relational databases to enable both informational and financial transactions (Erickson & Siau, 2008). The use of Web Services within the broader framework of Service-Oriented Architecture is similarly predicated on databases that can scale over time, aligning with the rapidly changing needs of enterprises that rely on complex data analysis to evaluate strategies and initiatives.

DBMS systems have progressed beyond being mere data repositories and have become knowledge systems that rely on enterprise data management and Master Data Management (MDM) approaches for aligning content, intelligence, and knowledge to specific strategic needs (Reagan & Rowlands, 2007). DBMS is now more synonymous with strategic planning than ever before, and has become embedded in many of the planning, execution, and monitoring processes of companies, including strategic market planning (Weinberger, 2004).

DBA Roles and Responsibilities

The roles and responsibilities of DBAs have changed significantly — from support staff who keep database software and systems running to professionals who complete complex projects as part of broader teams or independently. As a result, the DBA role is now characterized more by collaboration and problem-solving than by purely technical expertise. There needs to be a balance among collaboration, strategic vision of where the company is heading and how databases contribute to that direction, and the ability to translate user preferences and needs into real-time data modeling (Konana, Gupta, & Whinston, 2000). These requirements shift the DBA from a single contributor to a project management-oriented role. Consequently, the ability to continually manage and coordinate people, processes, and resources in alignment with critical-path timelines is one of the most important skills any DBA can develop.

In conjunction with this collaborative function, the DBA must also anticipate and respond to the need for making workflows as agile as possible and aligned to both system-user goals and internal requirements (Smith, Smarkusky, & Corrigall, 2008). DBAs' roles therefore also require establishing exceptionally clear communication processes between teams — particularly important because many DBAs are involved in developing internal applications that depend heavily on databases to deliver useful results.

While technical expertise remains essential, DBAs also need the ability to create significant value through strategies that impact the company positively over time. Studies have shown that the ability to translate and teach technical skills is as important as — if not more important than — pure technical acuity. It lies in the ability to teach others, assist them in reaching their goals, and help them see how their contributions make a meaningful impact on strategic initiatives and results (Smith, Smarkusky, & Corrigall, 2008). DBAs must be able to define roles within projects and create programs that lead to more complex, shared objectives over time. The DBA as a strategic-level project management leader also needs a high degree of shared accountability, transparency, and responsibility — all aimed at earning trust as a leader. DBAs must also nurture a shared sense of purpose and keep teams motivated to accomplish longer-term goals. As these requirements make clear, DBAs are much more than technicians who keep systems running; they are critical members of strategic teams who provide guidance and leadership in the attainment of complex, cross-functional goals and objectives.