This article can also be found in the Premium Editorial Download "Storage magazine: Comparing the top data backup packages."
Download it now to read this article plus other related content.
Today's DBA is one of the key protectors of the most valuable company asset--its data. With a growing amount of data moving from flat file systems to organized relational databases, the DBA's participation in database storage has never been more important. Understanding the storage environment and the options available on storage platforms will continue to become an increasingly important part of the DBA's job.
In the future, the DBA will be asked to take on even more storage responsibilities. Not only will the DBA be responsible for database storage, but will be held accountable for the database's performance, which is directly related to the optimal structure of the database and placement of data. This change in a DBA's responsibilities is mostly due to the change in organizational structures through the evolution of the company (see "
The evolution of complexity in the storage environment--for example, storage area networks (SANs), network-attached storage (NAS) and SAN/NAS hybrids--is also changing the DBA's role within IT. There's no longer the simple server and captive storage structure in most environments. Going forward, DBAs must be aware of the fabric (whether Fibre Channel or Ethernet) and highly developed software features available on advanced storage subsystems. The end result is DBAs will be more closely integrated with the storage hardware and software decisions and ultimately will be responsible for looking for ways to leverage these new features for better database administration. To understand this further, let's look at the critical storage layers a DBA must interface with.
The storage layers represent the interface DBAs use to build a database with the appropriate characteristics. Information flows from business needs to define application requirements. The DBA takes these requirements directly from the application programmers. From the bottom up, hardware sophistication provides a platform for the software options that need to be understood by the DBA. Let's look at each layer individually.
Lines of business. It's only common sense that the earlier the DBA knows and understands the direction of the company, the better prepared for future requests they'll be. This is best accomplished through formal communication with the lines of business. Whether it's through e-mail, phone calls or regular meetings, the DBA benefits from storage information gained at these planning sessions.
Application. From the lines of business, applications are constantly being created and changed. The communication between the application programmers and the DBAs is critical. Much like interfacing with the lines of business, the sooner the DBA can get involved in the application change/creation process, the better. Knowing the type of data, availability and performance requirements of the application helps the DBA plan their storage strategy.
Hardware. The last thing a DBA should have to worry about is hardware. But because storage can have such a dramatic effect on performance and availability, it should be on the mind of every DBA. The DBA doesn't need to know the detailed architecture of the storage subsystems, but it helps to know some key components such as cache, channel type, drive size and rotational speed. Once these components are known, the DBA can identify the class of storage that would best fit the database being created.
When identifying storage software options, the DBA should be most concerned with performance and availability (See "Software tools" above). Software that increases performance--such as striping and other RAID techniques--should be implemented. Other storage software such as dynamic multipathing and channel load balancing can increase performance. Availability can be improved through mirroring software or advanced remote replication tools for disaster recovery.
If a DBA knows a new application is being created by a line of business and the application will be read-intensive, they can then request storage. Enterprise class storage using mirroring hardware is available. The informed DBA requests storage on this enterprise-class subsystem that also has the ability to pre-fetch sequential read requests into cache.
This was first published in March 2003