Database Archiving

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

This book is a practical guide for managing archiving projects with SAP R/3 efficiently. Hereby it is addressing both R/3 consultants, system administrators and key-users. Detailed solutions for optimal archiving strategies as well as the manual for a comprehensive database analysis are provided in this book. But thereby not only the technical side, but also the business side of data archiving is taken into account. Thus the reader will be able to implement an archiving project.

Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification. A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it’s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need—determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs—giving developers the valuable advice they need for building effective software requirements

Before major changes, ALWAYS backup your system. Before making major changes in the system, it is good idea to copy some data (sometimes all files) on a separate disk resource (or tape). Something can always goes wrong, a person can make mistakes. But if we have a copy of the data (backup) we are safe(r). Tools for performing data backup are discussed precisely in this micro-course.

The National Oceanic and Atmospheric Administration (NOAA) collects and manages a wide range of environmental and geospatial data to fulfill its mission requirements-data that stretch from the surface of the sun to the core of the earth, and affect every aspect of society. With limited resources and enormous growth in data volumes, NOAA asked the National Academies for advice on how to archive and provide access to these data. This book offers preliminary principles and guidelines that NOAA and its partners can use to begin planning specific archiving strategies for the data streams they currently collect. For example, the book concludes that the decision to archive environmental or geospatial data should be driven by its current or future value to society, and that funding for environmental and geospatial measurements should include sufficient resources to archive and provide access to the data these efforts generate. The preliminary principles and guidelines proposed in this book will be refined and expanded to cover data access issues in a final book expected to be released in 2007.

"This report... describes the meteorological satellite program of the United States, the data acquired, the applications of the data to climatology, the procedures for archiving the data, and plans for future meteorological satellites."--p.[1-1].

K2 blackpearl and the K2 platform is a large, powerful, "game-changing" application platform built on Microsoft technologies. Understanding it from top to bottom would be a great task for a single person, which is why we have gathered more than a dozen authors to supply you with the information to successfully transform your company into a process-oriented, efficient business that can grow with the K2 platform. Since this is the first book on K2 blackpearl, you will find a broad range of topics in this book, from the market in which K2 blackpearl is aimed to the architecture of the platform, from how to approach process design to developing your own custom user manager. The first part of the book is meant for everyone and provides an understanding of K2 blackpearl and where it fits in the marketplace. It is included to provide a framework for thinking about various aspects of process-driven applications, including how they differ from business process management techniques; identifying processes in your company to automate, the different pieces that make up a process; measuring the success of your efforts; and finally shifting your company's culture in the direction of process efficiency. This section may be the only section you need to read if you are sponsoring a process improvement effort in your company. If you are responsible for leading the effort, make sure to read Chapters 3 and 4. The other parts are meant to provide details on how to effectively deploy and use K2 blackpearl and include a broad range of topics. Read what you are most interested in, but also make sure to read Chapter 8, which will give you a great foundation to start designing processes with K2 blackpearl. Chapter 14 is also recommended for everyone because it provides an overview of the available K2 Designers and how you can share projects among them. K2 blackpearl is the main subject of this book, although we devote an entire chapter, Chapter 23, to the add-on product K2 connect to give you an understanding of how to bring SAP data into your processes. We also talk a bit about K2 blackpoint, particularly in the SharePoint chapters. Since K2 blackpoint is built on the K2 blackpearl foundation, many of the same concepts apply to that product as well, but we do not point out the differences between K2 blackpearl and K2 blackpoint. For that information browse to www.k2.com.