1

Topic: How correctly to transfer changes from test to fighting basis?

Colleagues greetings. Share your practice. How correctly to organize transfer of changes from test  in the fighting. The situation following - is 2 servers. On one there is a fighting basis, on the second the same test. Every day in fighting  the data. How correctly to transfer changes from test in fighting (structure changes) and how to update the data the test?

2

Re: How correctly to transfer changes from test to fighting basis?

msleg wrote:

Colleagues greetings. Share your practice. How correctly to organize transfer of changes from test  in the fighting. The situation following - is 2 servers. On one there is a fighting basis, on the second the same test. Every day in fighting  the data. How correctly to transfer changes from test in fighting (structure changes) and how to update the data the test?

SSDT, TFS, separate branches of the code for test and fighting, transfer of already tested functional from one branch in another merga at level change set.

3

Re: How correctly to transfer changes from test to fighting basis?

- Update fighting only migration scripts
(create\alter + saving of the data in temporary tables and  back after update if it is necessary)
Script to receive from TFS or each developer writes small  under specific , before release all these  gather in one.
- Update of the test with  through a raising   (if  there is no possibility, diff or a broad gull)
Further roll a migration script (at the same time checking that it joins without incidents)

4

Re: How correctly to transfer changes from test to fighting basis?

msleg;
Transfer of a script to fighting basis is process which should not become automatically in any way.
1) Should be prepared  for development. All should be checked up and viewed eyes.
2) It is desirable to take  fighting basis to tear it on a test server and to roll a script on it. It gives the flavor about development time. Because change of columns in huge tables can occupy long time or not end generally. Probably it will be necessary to create the second table to transfer there the data, to rename back. Probably there will be other problems which you do not see on a test DB.
3) On a fighting DB it is necessary to declare  if it is necessary. To stop a software which works from a DB, to notify owners of systems contacting to a DB.

5

Re: How correctly to transfer changes from test to fighting basis?

Generally speaking visual studio is able to compare projects and bases and  a script
But  it is finite not so variant
Though, why would be not present

6

Re: How correctly to transfer changes from test to fighting basis?

We use RedGate SQL Compare, and also it is prepared migration scripts.
All the same it is necessary to look that it there , for the big tables normally it is necessary to write hands, also if for example you in  to basis have an index which was both in fighting, and in it added a new field it will be generated  an index and creation new that at the loaded system causes a problem.