Database Archiving - Olson_ Jack E_.pdf - Database Archiving (2724) - superktos86

Morgan Kaufmann Publishers is an imprint of Elsevier

30 Corporate Drive, Suite 400, Burlington, MA 01803, USA

Designations used by companies to distinguish their products are often claimed as trademarks or

registered trademarks. In all instances in which Morgan Kaufmann Publishers is aware of a claim, the

product names appear in initial capital or all capital letters. All trademarks that appear or are

otherwise referred to in this work belong to their respective owners. Neither Morgan Kaufmann

Publishers nor the authors and other contributors of this work have any relationship or affiliation

with such trademark owners nor do such trademark owners confirm, endorse or approve the

contents of this work. Readers, however, should contact the appropriate companies for more

information regarding trademarks and any related registrations.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any

form or by any means—electronic, mechanical, photocopying, scanning, or otherwise—without

prior written permission of the publisher.

Permissions may be sought directly from Elsevier’s Science & Technology Rights Department in

Oxford, UK: phone: (+44) 1865 843830, fax: (+44) 1865 853333, E-mail: permissions@elsevier.com .

You may also complete your request online via the Elsevier homepage ( http://www.elsevier.com ) , by

selecting “Support & Contact” then “Copyright and Permission” and then “Obtaining Permissions.”

Library of Congress Cataloging-in-Publication Data

Application submitted.

ISBN: 978-0-12-374720-4

For information on all Morgan Kaufmann publications,

visit our Web site at: www.mkp.com or www.books.elsevier.com

Printed in the United States of America.

08 09 10 11 12 5 4 3 2 1

I dedicate this book to my grandchildren:

Gavin, Harper, and Dru—and grand they are!

Preface

This book is about archiving database data. It is not a general purpose book

about archiving. It is also not a book about archiving any or all kinds of data.

It is about archiving data in traditional IT databases (e.g., relational databases,

hierarchical databases, and structured data in computer files). Examples of

source data for archiving are data in DB2 DBMS systems on IBM mainframe sys-

tems, data stored in VSAM KSDS databases on IBM mainframes, and data stored

in Oracle DBMS systems on Unix servers. It does not include data in spread-

sheets or smaller relational systems such as Microsoft Access databases on desk-

top computers.

This perspective might seem narrow; however, this is a critically important

emerging topic in IT departments worldwide. Actually I should say that the

topic

emerged. The need to archive database data is showing up every-

where, although the database tools industry has been slow to provide tools,

methodologies, and services to effectively accomplish it. Most IT departments

know that they need to have an effective database archiving practice and are

trying to figure out how to build one.

has

The data that needs to be archived from databases is generally the most impor-

tant business data enterprises keep. It must be retained under very strict rules

as specified by laws and common sense. These are not small amounts of data.

The archival stores will eventually reach data volumes unheard of even by

today’s standards.

Archiving is becoming a much more important topic because it is a part of a

major shift in thinking about data that is occurring throughout the United States

and most of the rest of the world. This shift demands that enterprises manage

their data better than they have in the past and manage it in a way that serves

constituents other than the operating departments of an enterprise. The con-

stituents I am talking about include auditors (both internal and external), gov-

ernment investigators, customers, suppliers, citizens’ groups, and plaintiff

lawyers for lawsuits filed against corporations. Data is becoming more public

in that it reflects a company’s activities and performance. As such, it must stand

up to rigid scrutiny and be defended as accurate and authentic.

The constituent base also includes businesspeople within the enterprise who

are not trying to assert a wrongdoing or to defend against one but rather who

legitimately want to look at historical data to achieve some business goal.

Although some will say that this is the role of a data warehouse and business

intelligence, the reality is that data warehouse data stores generally do not go

xiii

xiv

Preface

back more than two or three years. Sometimes you need to reach back farther,

and thus the database archive becomes the logical source.

Archiving data is one facet of this massive change in thinking about managing

data. Other parts are database security, database access auditing, data privacy

protection, data quality, and data clarity.

The principles of archiving database data are not particularly different from

archiving anything else, viewed from the highest level. However, viewed from

a low level, the details of database archiving are very different from archiving

other types of data. This book drills down into the topics that a database archi-

vist needs to know and master to be effective.

Since there has been no need or attempt to archive database data until

recently, there’s no large body of experts who can guide an IT department

through the process of building an effective database archiving practice. In

fact, for most IT departments, there are no experts sitting around and little

or no organized practice. Everyone is starting on a new venture that will

mature into a standard practice in a few years. For now, on your journey

you will undoubtedly encounter many stumbling blocks and learning

experiences.

In addition to a lack of experts, there is a lack of educational material that can

be used to understand how to become a database archivist. Hopefully this book

will reduce that shortcoming.

HOW THIS BOOK IS ORGANIZED

Before getting too deep into database archiving, it is helpful to begin by looking

at the generic process of archiving to determine some basic principles that

apply to archiving just about anything. Understanding these concepts will be

helpful in later grasping the details of database archiving.

From the basics, the book moves on to discussing how a database archiving

project comes into existence, gets organized, and acquires basic goals and poli-

cies. This is an area that is poorly understood and yet crucial to the success of

database archiving projects.

This discussion is followed by a detailed treatment of designing a solution for a

specific application. All the factors that need to come into play are discussed, as

are criteria for selecting one path versus another.

A description of software required to execute a database archiving application

follows the discussion of database archiving design. The strengths and weak-

nesses of various approaches and the features that you should look for are all

analyzed.

Database Archiving - Olson_ Jack E_.pdf

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: