Activity Monitoring for Database Management

Only a few years ago, most database administrators (DBAs) mainly concerned themselves with file storage space. Much of our time was spent tracking the use of disk space and determining how much was used and what was usable. That’s still happening today but has been extended to suit the more complex DB structures of today. We name this FAM and DAM, or FAM-DAM (management of file operation, management of database operation). Learn more at managing database.

Such DBA practices usually boil down to three items being monitored: 1. Logging to event (on the host server) 2. Passive control of network traffic on host Server 3. Agents or client applications on individual machines FAM-DAM is where much of the day-to-day work takes place in the DBA’s language. Many nightmare situations and severe problems can be avoided with successful FAM-DAM. It is especially important on the cloud-based and virtual computing services of today.

Let’s look at each of these three management strategies, and how they allow the DBA (and thus the clients of the administrator) to maintain a stable database.

Event Logging (on a host server) Many services on every server type must log events occurring within that service. They have broad applications for service-specific monitoring and evaluation of problems but are not as effective on a server-wide scale. To save money, logging on to the entire server is always switched off by default, but most professional DBAs can use log-and-event managers. Those keep from getting out of hand the otherwise big event logs.

To this end, there are hundreds of resources, most server-specific. However, without a good event log, an administrator is not only unable to easily control what’s happening on the server itself, but is also unable to easily back-track issues to fix. Restauration and maintenance practices was assessed at 90 per cent. Reducing as much of this as possible saves money and makes services quicker.

=== Passive Network Traffic Monitoring (on the host) It is important to track the network traffic that feeds both the host server and all linked services to go along with host server logging. Knowing the FAM-DAM traffic patterns and frequencies for database servers not only tells the DBA what to expect, but also where enhancements or adjustments can be made to handle traffic spikes better.

There are myriads of traffic control approaches. Computer solutions for smaller networks are a popular low-cost solution although resource management is best for the hardware choices for larger area networks. They provide the DBA with details about which customers connect and when, how the applications or database respond to those requests, and how easily the details flows in either direction.

When updating or changing network services this knowledge will prove crucial. This may also be critical when troubleshooting network problems or individual programs. Most device crashes are triggered simply by overload access.