Post reply

What is Prod,Dev and Test servers?

  • January 12, 2012 at 8:13 am

    #391295

    Hi Experts,

    Could you please explain me the purpose of the prod,dev and test servers? or share me if any web resource for understanding the differences of those three servers.

    Thank you,

  • January 12, 2012 at 8:20 am

    #1432555

    Production - Where the live application's database runs

    Development - where development is done

    Testing - Where new development/modifications are tested before been moved to production. Also called QA or UAT.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 12, 2012 at 8:23 am

    #1432560

    & the Web resource: http://openlearn.open.ac.uk/mod/oucontent/view.php?id=399373&section=1.2

  • January 12, 2012 at 8:24 am

    #1432562

    thank you for answer.I have one doubt.

    users are connecting to prod and then some modifications are done in prod databases.

    how to maintain same data in test environment?

  • January 12, 2012 at 8:28 am

    #1432571

    Many possible ways. You can replicate (not common but done), you can use a database sync tool like SQLDataCompare, you can restore the production backup each night/weekend, probably several more.

    However, test probably shouldn't contain the same data as production, especially if you're working with any financial data. There are data protection and data security laws and confidential data can't just be copied to dev where lots of people have unrestricted access to it.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 12, 2012 at 8:37 am

    #1432578

    Thats very good explanation.I have one more doubt plz.

    iam assuming i have maintaining 140 servers in that 60 prod.total 100 db's are there in prod.now my doubt is how these db's are created in 60 servers.and how many instances we create for each server?

    or one instance = one server? please clarify.

  • January 12, 2012 at 8:40 am

    #1432580

    Huh? If you're maintaining 60 prod servers you should know how the databases are spread out. Or ask your senior DBA.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 12, 2012 at 8:45 am

    #1432590

    The idea is related to workflow and testing, and making sure you have a decent (rigid) testing dfunctionality before anything gets deployed to "production"

    first, what are we trying to avoid: here's a realworld scenarion:

    a DEVELOPER decides a change is in order , and makes the change directly in production at 11:50, then goes to lunch for an hour, or a doctors appointment, or whatever.

    ten minutes out the door, eveyone is starting to report problems..they cannot work, the system is hanging, whatever.

    the core issue is the developer made a change that was not tested and validated and finally approved , and the proposed solution was either wrong, or had farther reaching impacts than he originally thought out.

    to avoid that, you want to go through at least beta-level development, and then testing/Quality Assurance testing before it goes into production.

    Developers work in the dev server; they may add columns, tables, objects, take them away, whatever as they see fit .

    once they have what they think is a solid code base, they would pass schema changes, pluss the application that matches those changes to the DBA.

    He would put the schema changes on the Test server, and the Test group would test the updated application.

    If anything did not work, the Test group would kick back any issues to the dveloper.

    Only after the Test group has approved a specific set of matching application and data changes, would the "production" area, both the application and the data, be updated with those new changes.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • January 12, 2012 at 8:50 am

    #1432598

    Thank you lowell

  • January 12, 2012 at 9:27 am

    #1432667

    jr.sqldba (1/12/2012)

    Thank you lowell

    you are very welcome! good luck!

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Viewing 10 posts - 1 through 9 (of 9 total)

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