SQL Source Control refreshing after every commit

tony840

I have some databases set up to use SQL Source Control 6 to commit schema changes, but I'm finding the process quite annoying in that if there are several different sets of changes to commit, I select a subset of changes, supply a log message, commit them, and it then insists on going through the rather lengthy refresh process before I can commit the next set.

Can I either:

1. Make the refresh manual, so hopefully it will just remove the changes I have committed from the list, and allow me to commit others without a refresh.

2. Switch an existing configuration for a database so that SQL Source Control only scripts the changes, and then I can use local tools to actually do the commits. I think that was an option on set up, but can I change to that option without unlinking and re-linking the SQL Source Control support for the databases in question.

Thanks

Tianjiao_Li

Hi @tony840

At the moment, option 1 is not available yet and we have a rather popular request on our user voice forum. Please cast your vote if you'd like to support!
https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically

For option 2, it's actually something we often suggest users to do. You should link to a working folder. For more details please see: https://documentation.red-gate.com/soc6/linking-to-source-control/other-source-control-systems/link-to-a-working-folder

tony840

For option 2, I already have it set to do the change detection and then commit, including a list of some tables to control the data for. I was hoping I could turn the commit part of it off for the existing setup, rather than having to start again and go through tagging the tables to be included.