Comments
5 comments
-
Hi @MLysons
Absolutely, what you can do here is use SQL Source Control as the Source type in SQL Compare and then link to the local clone for that database, then you can select a specific revision or the latest and compare to your test server.
-
Thanks for the answer, @DanC
I have figured out the approach you suggested and it does work
I was really wondering if we could set the actual remote as the source rather than a local, cloned repo? From your answer, I assume that's not possible with SQL Compare?
-
Hi @MLysons
Glad to hear that approach worked!
Unfortunately, the tool is limited to looking at local sources or across networks, rather than remote online. In this case, I would suggest mentioning it as a suggestion on the UserVoice here: https://redgate.uservoice.com/forums/141379-sql-compare
-
Awesome - thank you very much.
-
You're most welcome if you need further help feel free to reach out to us on support directly!
Add comment
Please sign in to leave a comment.
I am proposing to use Git with SQL Source Control, such that each developer (4 of us) will have our own copies of the database which we link to our local repository. The local repository will be a clone of a remote repository. When a dev commits changes locally and initiates a pull request we will then merge the changes into the main branch on the remote repository. This part is working as intended.
From there, I want to be able use the latest version of the main branch of the remote as a SQL Compare source to compare against the database on the test server.
Is this possible? Is there a better way of doing this?