19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Hardware & Software Remarks<br />

____________________________________________________________________ .........................................<br />

S 4.70 Monitoring a database<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: Administrators<br />

Databases should be monitored regularly to ensure the availability, integrity<br />

and confidentiality of their data. <strong>The</strong> essential items which need to be<br />

observed in this respect are described briefly in the following.<br />

<strong>The</strong> database should be checked for fragmentation at regular intervals in order<br />

to permit a timely planning and implementation of any required measures such<br />

as reorganisation of the database.<br />

As a rule, database systems manage the memory available to them in the form<br />

of blocks having a fixed size. If data records are inserted into an empty table,<br />

new blocks are reserved for this table and filled with the data records. <strong>The</strong>se<br />

newly created blocks can be utilised almost fully (with the exception of the<br />

last block).<br />

If data records are deleted during subsequent operation, the memory blocks<br />

which were occupied by them are released. In principle, this memory space<br />

can be used by other data records. However, as the data records have different<br />

lengths, 100% utilisation of the free memory space is usually not possible.<br />

Consequently, modifications to data in the course of time result in an<br />

increasing number of gaps in the database blocks, most of which can no longer<br />

be utilised. Such gaps are created not only by DELETE- and INSERT<br />

operations but also by UPDATEs, as a data record can no longer be stored at<br />

the same location once its length has been changed.<br />

<strong>The</strong> presence of such gaps not only increases memory requirements but also<br />

retards the operation of the database, as more disk space needs to be covered<br />

in search of data records and free memory.<br />

<strong>The</strong> degree of fragmentation in the blocks of a table can be ascertained by<br />

comparing the quantity of data in the data records of the table with the<br />

memory space occupied by the blocks of the table. In the case of certain<br />

database management systems, an analysis of the degree of fragmentation is<br />

also supported by the accompanying administration software or add-ons.<br />

If a database becomes excessively fragmented due to the scenario mentioned<br />

above, a reorganisation needs to be performed. This can be done manually, for<br />

example, by exporting all the data out of the database, re-computing and recreating<br />

all the tables, and then importing the data back into the new database.<br />

Auxiliary programs for de-fragmenting tables are also available for some<br />

database management systems.<br />

Similarly, the available space of the database files should be checked regularly<br />

in order to permit a timely planning and implementation of any required<br />

measures such as the extension of the memory capacity. Some database<br />

management systems allow administrators to prevent excessively rapid<br />

fragmentation by already defining certain parameters during the creation of<br />

the tables. For instance, it is possible to reserve a particular number of<br />

consecutive blocks for a table in advance, to save free memory for any<br />

changes required during later operation.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!