question

erlokeshsharma08 avatar image
erlokeshsharma08 asked

UAT Environment

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
test
1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ASK SQL Server Central runs by you voting. For all helpful answers below, please indicate this by clicking on the thumbs up next to those answers. If any one answer lead to a solution, please indicate this by clicking on the check mark next that answer.
0 Likes 0 ·
ThomasRushton avatar image
ThomasRushton answered
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.
3 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thanks Thomas I also suggested the same point. We get the data in prod through etl jobs on daily basis. and we release things into prod on weakly basis. So I think PROD to UAT refresh activity would be once every week. How do you ensure that the source control's copy of objects and the one in prod are same, or it is solely the responsibility of the developer working
0 Likes 0 ·
Good question. I don't. I don't have access to the development environments at all, so I rely on getting appropriate release scripts to update the various test & production instances. What's supposed to happen going back is that, when we refresh the UAT databases, we also refresh (and anonymise) the QA & Development environments - so that they all have up-to-date schemas & data loads. It's then down to the development team to make sure that the scripts they provide to me do the job that's required of them!
0 Likes 0 ·
Hmm May we need to replicate the same scenario here. Thanks Thomas
0 Likes 0 ·
Venkataraman avatar image
Venkataraman answered
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.
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.