locked
Using SQL Server with different levels RRS feed

  • Question

  • Hello everybody<o:p></o:p>

    I'm working recently on a Project which has 2
    different Databases. A Database is Production Database and the other is development database. They have defined the development DB for developing and the production is only for using. Is it a good idea or is it a standard strategy?<o:p></o:p>

    I’m a software engineer and working about 8 years butI had never seen a structure like this. <o:p></o:p>

    <o:p> </o:p>

    Thanks<o:p></o:p>



    Regards Parisa

    Monday, July 11, 2016 8:29 AM

Answers

  • Hi Parise,

    It is good one. IF you make a mistake it will not affect in production . What are the changes done in development just make sure and change in production database during release.

    Monday, July 11, 2016 8:35 AM

All replies

  • Hi Parise,

    It is good one. IF you make a mistake it will not affect in production . What are the changes done in development just make sure and change in production database during release.

    Monday, July 11, 2016 8:35 AM
  • Thanks for the answer.<o:p></o:p>

    Do we have a tool or Feature in SQL Server to list the
    changes if I forget what I have done? Or something likes check in to Transfer
    the changes to another DB?
    <o:p></o:p>



    Regards Parisa

    Monday, July 11, 2016 10:08 AM