Hi Folks, Want your suggestions for the environment that we are using in our organisation. We have created 4 environements as far as viewing the report is concerned (report managers). These are 1. Development 2. Testing 3. UAT 4. Production Now at the backend we have two databases --- Dev and Prod. Each of the above environment uses different databases as 1. Development -- Dev 2. Testing -- Dev 3. UAT -- Prod 4. Production -- Prod For certain reports we want it to be tested on UAT before pushing it to PROD. In order to do so, at the back end we need to run stored procedures on PROD. However as this is still the testing we will not be checking in the code inside VSS. So due to this ambiguity we have scenarios where checked in code inside VSS is not consistent with the one in PROD. I am sure you guys might have encountered the same situation. How do you tackle this. Thanks
A few thoughts. 1. keep PROD dedicated to PROD. 2. UAT should be its own environment, as should Dev & test. Ideally these environments should all be isolated from each other - just for safety. 3. UAT database should closely match production for volumes. Where I currently am, we refresh the UAT database server with a copy of the production databases every quarter. And the code/application base likewise.
In our project, we have got a production backup being restored in Development environment on weekly basis and We create one more copy of production database for our development works. Whenever something goes wrong, we can take again copy of the current production version from restored production database. Generally, once a new release goes to production, production database backup is restored in development environment to start with for further development works. In your case, if you get production backup restored in development environment, you will be able to test it without issues. It is not recommended to test the code in UAT environment. As Thomas is telling, UAT environment, PROD envionment should be isolated. They should not be used for testing something in progress development code.