Database Management Systems

From a technical standpoint, Section 3 covers specific areas of technology to a greater or lesser degree of depth. Although many of the features that are contained within DBMSs are reflected in all the major products, there is a degree of diversity.

Section 3.1.1 looks in some depth at the issue of database replication. The reason why this has been covered so extensively is the impact it has on data replication and how that can be managed (covered in Section 4.1.5). Again, this demonstrates that, although there is a need to treat the two areas separately, the constraints within any given system may make that division more complex than it need be.

The second most important element of database functionality, back-up and recovery, is also extensively covered. Section 3.1.2 looks at strategies for backing up data (and more importantly, recovering that data) and also the different elements that need to be considered when creating a recovery strategy.

Having mentioned the second most important element, it is now time to consider Section 3.1.4, which covers security. The implementation of security within a database product can be problematic. SecuritySecurity is an enterprise issue, and as such has to extend past any implementation of database or application. This does not absolve the providers from having security aspects within their product offerings. Alles zu Security auf CIO.de

Although security has to be implemented at the highest level, covering the infrastructure and peripheral elements, this can only be achieved by having open standards within specific offerings that can be brought together into the security framework. Passing control of security to another part of the infrastructure is not the answer.