Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pras2007
Posting Yak Master
216 Posts |
 Posted - 2009-04-23 : 21:05:56
|
| Hello All,Our organization has the following environment already established: - Test - QA - Production The problem we are having is poor change control of the environments. The following are questions that I have concerning the environment: - How would I insure that the databases always in sinc with each other (Test, QA, Production)? - We have 5 developers, should each developer have their own environment until the project reaches production? - How are you guys able to control your environments? Please advice. Thanks. |
|
|
nwalter
Starting Member
39 Posts |
Posted - 2009-04-24 : 12:01:41
|
| One database? Many databases? You probably don't want to sync your QA and test environments with your production environment. You could do regular restores of your production environment to your QA and test but you will wipe out any changes in progress on QA and test so your developers need to know when it is happening and prepare.You really just need to implement policies and procedures. If that fails and your developers still run nuts with your environment you can use DDL triggers to either log or block changes to the database and force a change management process on them. |
 |
|
|
|
|
|
constructing a better SQL Server 2005 Environment