With the amount of data a business accumulates now doubling every 12 to 18 months, IT professionals need to know how to develop a system for archiving important database data, in a way that both satisfies regulatory requirements and is durable and secure. This important and timely new book explains how to solve these challenges without compromising the operation of current systems. It shows how to do all this as part of a standardized archival process that requires modest contributions from team members throughout an organization, rather than the superhuman effort of a dedicated team. * Exhaustively considers the diverse set of issues-legal, technological, and financial-affecting organizations faced with major database archiving requirements. * Shows how to design and implement a database archival process that is integral to existing procedures and systems. * Explores the role of players at every level of the organization-in terms of the skills they need and the contributions they can make. * Presents its ideas from a vendor-neutral perspective that can benefit any organization, regardless of its current technological investments. * Provides detailed information on building the business case for all types of archiving projects... 131 transforming of, 130a131 DBMS archive data store, 133 relational and non relational data sources, 132 system, elements, ... policy, 247a248 purpose of, 245 and testing, 243 responsibilities for, 244 trails of, 245a246 Automated teller machine (ATM) transactions, 41 ... 245 application entity-relationship diagram ( ERD), 95 architects, 100 See also (Entity-relationship diagram) archives, 108a 109, anbsp;...
|Author||:||Jack E. Olson|
|Publisher||:||Morgan Kaufmann - 2010-07-28|