NoSQL Zone is brought to you in partnership with:

I’ve been a Windows developer since 3.0 and caught the Visual Basic wave early with v1. I’ve released a “production” application in every version of VB since then (except VB for DOS). Focusing on enterprise, line-of-business development I’ve built Call Center Applications, Mortgage finance systems, Customer Relationship Management tools and more recently I’ve been in the Litigation Support/Electronic Data Discovery/Electronically Stored Information space. Greg is a DZone MVB and is not an employee of DZone and has posted 480 posts at DZone. You can read more from them at their website. View Full User Profile

Database Lifecycle Management Content on MSDN

  • submit to reddit


Database lifecycle management (DLM) is a policy-based approach to managing databases and data assets. DLM is not a product but a comprehensive approach to managing the database schema, data, and metadata for a database application. A thoughtful and proactive approach to DLM enables an organization to manage data resources according to appropriate levels of performance, protection, availability, and cost.

DLM begins with discussion of project design and intent, continues with database develop, test, build, deploy, maintain, monitor, and backup activities, and ends with data archive. This topic provides an overview of the stages of DLM that begin with database development and progress through build, deploy, and monitor actions (Figure 1). Also included are data management activities, and data portability operations like import/export, backup, migrate, and sync.

How to Use this Topic

Use the SQL Server Database Lifecycle Management diagram to identify the applications and actions that apply to your database scenarios. To get additional information about a specific DLM task, scroll down to the links and click a topic name.

To communicate with the author of this topic with comments or suggestions, send e-mail to Louis Berner: Please mark your message with Subject: “DLM topic on MSDN.”image 


This is something that every dev and app that stores data has had to deal with, updates and changes over time. This is interesting guidance and series of links. Looks a little complicated, but it's not an easy problem to solve either...

Published at DZone with permission of Greg Duncan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)