Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development & Delivery Professionals

Primary Analyst Photo Document Information Rate this Document

September 20, 2005

Removing Databases Should Also Be Part Of Your Enterprise DBMS Strategy

by Noel Yuhanna

This is an excerpt

Executive Summary

Removing databases is an uncommon practice in the industry. Why? Because it's more challenging than building a new one. The number of databases that each enterprise has continues to grow because of newer applications, and the need for development and maintenance of existing applications. Forrester estimates that more than 10% of all databases in enterprises are not used or are sparingly used and therefore, could be removed or archived, which can improve overall manageability and lower costs. Enterprises should look at removing databases on a regular basis through database consolidation, recycling among projects, and by eliminating unwanted databases.

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word: