Tuesday, March 4, 2014

DLM - Data Lifecycle Management



Going through my bookshelf, I came across an older title ‘High Performance SQL Server DBA’. Now being 9 years old, the scripts are no longer relevant. Before I consign this volume for recycling, I have made notes on the headings in Chapter 1 which summarises the DLM Ideology ‘Data Lifecycle Management ‘.
Data Lifecycle Management advocates that the life of data from its creation to removal can be managed by DLM.

The 3 components of DLM -

  1. Data Management Service Layer
  2. Database Management Service Layer
  3. Performance Management Service Layer


Data Management Service Layer

                Logical Data Management

  •  Data Definition – What the data represents.
  •  Standards Control – Consistent use of data types, naming conventions
  •  Documentation – Document code, standards etc.
  •  Metadata Management – Use a data dictionary for attribute & data type definitions.


                Physical Data Management

  • Physical Design
  • ETL / Data Integration
  • Data Profiling / Firewall
  • Data Archival


Database Management Service Layer
  • Database Management
  • Installation / Configuration
  • Storage Management
  • Schema Design / Management
  • Security Management
  • Backup / Recovery Management
  • Business Logic Construction / Analysis
  • Change Management
  • Job Management

Performance Management Service Layer

Performance Lifecycle Management

                Proactive Action
  • Physical Database Design
  • Proactive Performance testing
  • Change Management
                Monitoring - (3 Major Performance methodologies)
  • ·         Bottleneck Analysis
  • ·         Workload Analysis
  • ·         Ratio Analysis
    (Applying these both Ad-hoc & 24/7)
               Analysis
               Recording database performance information for trend analysis.
               Forecasting
                           Use of Analysis data to understand future needs

               Tuning
               Revisiting the database as needs change, usage differs and time progresses.
               Configuration, SQL Code & Physical design may all need to change over time

No comments: