Sign in / up

back to article From production to development databases (and back again)

In many organisations, it isn't just the production database that database administrators (DBAs) have to look after. There are several non-production versions, as well. Project teams may need one to develop on, so that they can work in isolation without affecting production. A QA team may need its own version for testing …

COMMENTS

House rules Send corrections
This topic is closed for new posts.
  1. Britt Johnston

    other reasons to replicate a database include...

    We requested a duplicate of a production database as a read-only version for interfacing (this was 1996, pre-virtual servers). It worked fine, was easy to replicate daily and reduced performance problems for input.

    More commonly, a lot of applications request a training version.They get wiped occasionally, can be used for integration testing, or can restore an input scenario before each course.

    0 0
This topic is closed for new posts.

Other stories you might like