Redgate SQL Source Control recommended workflow for dev-test-live databases

Question

We are trying to start with SQL Source management and ask some questions.

This is what I am striving for. Does this seem to work?

• Change dev / procs database tables
• Disable dev git branch on dev PC
• Push changes to the central repo
• Repeat steps 1-3 for each change.
• Merge dev branch into test branch
• Use ConGtrol "Get Last" SQL Source in Test Branch
• Apply changes to test database
• Repeat steps 5 through 8, but from the test to live

Note: - Use of the "General Database" development model.

Questions:

• Looks like this will work?
• Can SQL Source Control apply changes to test and live databases?
  • SQL Compare dev ?

• : http://goo.gl/l2mJdt
• Google Doc

Answer 1

, , .

( Red Gate)

• SQL Source Control . , , . SQL Compare , UAT/ . Red Gate Deployment Manager.

• Shared/Dedicated . , dev, . (, git), , , .

. , CI-, , . , .

Answer 2

, , . , - Migrations V2 , .

- , , , , SQL - , - TeamCity , , Test, , .

Answer 3

, , .

Red Gate ( ). SQL Compare.

, , , .

:

• • , /proc/etc.
• We also save the working folder on the dev server using a common model.
  • This allows us to use get-latest to update dev with fixes from live.

It might be easier if the function is a mixed model (Vote here ).