SQL Server Performance

Dev/Test/Prod Scenario

Discussion in 'SQL Server 2005 General DBA Questions' started by sani, Dec 7, 2010.

  1. sani New Member

    Hi All,

    I am looking for a solution to have Development, Test and Production environment so that developer just have fully access to development, I have no idea about Test environment, For Production just Read/Write access for all users including developer should be available and any necessary changes in meta data and database design will be done by DBA.

    So If you are using similar scenario Please let me know the detail.

    Thanks in advance,

    Sani.
  2. FrankKalis Moderator

    We have the production environment to which developers generally do not have any permissions. With some management approval a dev could get read-only access to production.
    On the test instance the database devs do have db owner access, the client developers get business users permissions assigned to enable them to test their code as if they were the business users. The test instance is also against which the client developers develop.
    The development instance is only for the database development. Once this is done, the code gets published to the test instance and depending on the change itself, it then either required client development and/or business users testing.
    Once everyone is happy with the test result, a change request is raised, a change script is generated, passed on to the DBAs and they then execute the script to bring the change to production.
    I have described this whole process in 2 articles that might be worth reading.
    http://www.sql-server-performance.com/articles/dba/change_management_p1.aspx
    http://www.sql-server-performance.com/articles/dba/database_change_management_2_p1.aspx

Share This Page