title: Redgate SQL Source Control recommended workflow for dev-test-live databases
body: <p>We are trying to get started with SQL Source control and have some questions.</p>
  
  <p>This is what I am aiming towards.  Does this look like it will work?</p>
  
  <ol>
  <li>Modify dev database tables/procs</li>
  <li>Commit to dev git branch on dev PC</li>
  <li>Push changes to central repo</li>
  <li>Repeat steps 1-3 for each change</li>
  <li>Merge dev branch into test branch</li>
  <li>Use SQL Source ConGtrol "Get Latest" on test branch</li>
  <li>Apply changes to test DB</li>
  <li>Repeast steps 5 - 8 but from test to live</li>
  </ol>
  
  <p>Note: 
   - Using "Shared database" development model.</p>
  
  <p>Questions:</p>
  
  <ul>
  <li>Does this look like it will work?</li>
  <li>Can SQL Source Control apply the changes to the test and live databases
  <ul>
  <li>or do I need to purchase a copy of SQL Compare for the dev server to perform this task?</li>
  </ul></li>
  </ul>
  
  <p><img src="https://docs.google.com/drawings/d/1KU1l73U9M1z21I9C4hvopLCe3tMLsoLWJZ7pfzeodeU/pub?w=960&amp;h=720" alt="enter image description here"></p>
  
  <ul>
  <li>Fix the diagram here: <a href="http://goo.gl/l2mJdt" rel="nofollow">http://goo.gl/l2mJdt</a></li>
  <li>More notes &amp; experiences in my <a href="https://docs.google.com/document/d/1DaQ_F8ZdE1SuxESenOi45EoV9Tv0ZZ2DQwW-TprJT_I/edit#heading=h.xg5966aa21vl" rel="nofollow">Google Doc</a></li>
  </ul>