| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNISA996339087703316 |
|
|
Autore |
Morris John |
|
|
Titolo |
Practical data migration [[electronic resource] /] / John Morris |
|
|
|
|
|
Pubbl/distr/stampa |
|
|
Swindon, : British Computer Society, c2006 |
|
|
|
|
|
|
|
ISBN |
|
1-78017-059-9 |
1-906124-46-9 |
|
|
|
|
|
|
|
|
Edizione |
[1st edition] |
|
|
|
|
|
Descrizione fisica |
|
1 online resource (227 p.) |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
|
|
Soggetti |
|
Database management |
Electronic data processing |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
|
|
|
|
|
Nota di contenuto |
|
""Copyright""; ""Contents""; ""List of Figures and Tables""; ""Author""; ""Foreword""; ""Glossary""; ""Preface""; ""Introduction""; ""Part One Reasons and Methods""; ""1 Reasons""; ""WHY QUALITY DATA MIGRATION MATTERS""; ""A PRACTITIONER'S PERSPECTIVE""; ""2 The Golden Rules""; ""THE MOST IMPORTANT LESSONS""; ""3 Data Stakeholders""; ""INTRODUCTION""; ""THE COMMUTER AND THE KNIGHT ERRANT""; ""OWNERSHIP""; ""FINDING THE RIGHT FELLOW TRAVELLERS""; ""4 Four Key Concepts""; ""FIRST: A HEALTH WARNING""; ""USING CONCEPTUAL ENTITY MODELS TO DEFINE THE KEY BUSINESS DATA AREAS"" |
""DOCUMENTING KEY BUSINESS DATA AREA RELATIONS""""DOCUMENTING INDIVIDUAL KEY BUSINESS DATA AREAS""; ""CONFUSING DATA STRUCTURES AND BUSINESS FUNCTIONS""; ""LEGACY DATA STORES""; ""DOCUMENTING LEGACY DATA STORES""; ""5 Data Quality Rules""; ""INTRODUCING DATA QUALITY RULES""; ""A TYPICAL DATA QUALITY RULE DOCUMENT""; ""DATA QUALITY ASSESSMENT""; ""METHOD STATEMENTS""; ""METRICS""; ""GENERATING DATA QUALITY RULES""; ""6 Data Gaps and Data Mapping""; ""HEALTH WARNING""; ""STANDARD DATA MIGRATION TERMS""; ""DATA GAP ANALYSIS""; ""DATA MAPPING""; ""7 Non-functional Requirements""; ""INTRODUCTION"" |
|
|
|
|
|
|
|
|
|
|
|
""DATA SIZING""""RUN TIMES""; ""SEQUENCING""; ""HARDWARE AND SOFTWARE CONSIDERATIONS""; ""WINDOWS OF OPPORTUNITY""; ""DATA MIGRATION IMPLEMENTATION FORMS""; ""FALLBACK""; ""THE JONE WAY STREET' PROBLEM""; ""Part Two Specimen Project""; ""8 Project Overview""; ""INTRODUCTION""; ""SPECIMEN PROJECT OVERVIEW""; ""WHY A SEPARATE PROJECT?""; ""BACK TO THE EXAMPLE PROJECT""; ""USE OF ITERATION""; ""PROJECT CONTROL POINTS AND PLANNING""; ""9 Stage 0 Project Initiation""; ""INTRODUCTION""; ""STANDARD PROJECT INITIATION DELIVERABLES""; ""CREATE YOUR OWN DATA MIGRATION STRATEGY"" |
""FIRST-CUT PROJECT PLAN""""SET UP AN APPROPRIATE PROJECT SUPPORT OFFICE FUNCTION""; ""INITIAL LISTS OF DATA STORE OWNERS, LEGACY DATA STORES AND KEY BUSINESS DATA AREAS""; ""STAGE 0 CLOSEDOWN""; ""STAGE 0 PROJECT CONTROL POINTS""; ""10 Stage 1 Data Preparation""; ""STEP 1.0: STAGE INITIATION""; ""STEP 1.1: ANALYSE LEGACY DATA STORES""; ""STEP 1.2: UPDATE KEY BUSINESS DATA AREA MODELS""; ""STEP 1.3: CREATE FIRST-CUT SYSTEM RETIREMENT POLICIES""; ""STEP 1.4: CREATE DATA QUALITY RULES""; ""STEP 1.5: ENACT DATA QUALITY RULES""; ""DATA TRANSITIONAL RULES""; ""TRANSIENT DATA STORES"" |
""USE OF RECURSION""""STAGE 1 CLOSEDOWN""; ""STAGE 1 PROJECT CONTROLS""; ""11 Stage 2 Data Preparation""; ""STEP 2.0: STAGE INITIATION""; ""STEP 2.1: NOMINATE CANDIDATE LEGACY DATA STORES""; ""STEP 2.2: CREATE STAGE 2 DATA QUALITY RULES""; ""STEP 2.3: ENACT DATA QUALITY RULES""; ""STEP 2.4: ENHANCE SYSTEM RETIREMENT POLICIES""; ""DATA TRANSITIONAL RULES""; ""TRANSIENT DATA STORES""; ""STAGE 2 CLOSEDOWN""; ""STAGE 2 PROJECT CONTROLS""; ""12 Stage 3 Build, Test and Go Live""; ""STAGE 3 OVERVIEW""; ""STEP 3.0: STAGE INITIATION""; ""STEP 3.1: PHYSICAL DESIGN OF MIGRATION"" |
""STEP 3.2: DATA MIGRATION TESTING"" |
|
|
|
|
|
|
Sommario/riassunto |
|
Ensuring the success of data migration projects is crucial, especially if a business is looking to achieve maximum return on its investment. By following the best practice model devised by the author, a smooth and problem-free migration can be assured. The guide contains techniques and strategies blended with real-life examples and clear definitions of the most commonly used terminology. It debunks the mysteries that surround this subject, providing a template for judging the performance of in-house or brought in skills. For the IT practitioner who has been given responsibility for managing |
|
|
|
|
|
|
|
| |