Post reply

QA environment design

  • June 12, 2007 at 10:03 am

    #73199

    Good morning,

    I am a DBA and my boss recently recommended that we change our QA environment so that we don't have any databases on it unless they are actively being tested. Boss's argument of course is to save hardware costs.

    I'm not sure how i feel about this idea. The only logic i can think of at this point is that promotion to our QA environment would take up to 2 hours for some of our larger databases if we have to restore production databases to qa for every QA run.

    I am interested in any opinions out there from seasoned DBAs/Developers. Has anyone worked with this type of QA environment before? (I have only ever seen it where QA is a full copy of prod).

    Thank you kindly.

  • June 13, 2007 at 2:03 pm

    #712748

    Performance test may need a full copy of the current production database assuming the data is valid for testing.

  • June 14, 2007 at 10:14 am

    #713003

    You could try to outline the time and money for efforts expended for keeping no databases other than the ones being tested on the QA server. Then it might be easier to justify the presence of the databases.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • June 14, 2007 at 10:19 am

    #713006

    Thanks! I did just that and they came back saying it's too much time and effort to keep copying prod to qa for testing. so we're going with the "normal" method of having all dbs loaded in qa.

    thanks everyone!

  • June 14, 2007 at 10:23 am

    #713008

    While I'll be ...

    A 'common sense' decision made by management !

    Is your company looking for DBA's ?

     

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply