Options
SC4 - one license, multiple devs
ddodge2
Posts: 6
Hello!
I am in a situation where I have multiple devs and one copy of SQL Source Control 4. We currently are using BitBucket w/git protocol. I'd like to take an occasional snapshot of things (stored procedures, schemas, etc) for reference. No need for data and I'd like to ensure that in setting up source control that this will not, in any way, impede the other devs. Essentially I want to use this for a certain level of protection as I begin the process of reining in the wild west.
I had not yet found the answer to this specific scenario so thought I'd ask where in the documentation this might be or what you good folks might have to suggest.
Thanks!
Doug
I am in a situation where I have multiple devs and one copy of SQL Source Control 4. We currently are using BitBucket w/git protocol. I'd like to take an occasional snapshot of things (stored procedures, schemas, etc) for reference. No need for data and I'd like to ensure that in setting up source control that this will not, in any way, impede the other devs. Essentially I want to use this for a certain level of protection as I begin the process of reining in the wild west.
I had not yet found the answer to this specific scenario so thought I'd ask where in the documentation this might be or what you good folks might have to suggest.
Thanks!
Doug
Comments
You can use SQL Compare to take a snapshot of the schema, by creating a comparison project and set the Git Repository as the source and a Folder as the target.
Please read for more detail:
http://documentation.red-gate.com/displ ... comparison
Please note that the repository already keeps a version history which you can check in SQL Source Control:
http://documentation.red-gate.com/displ ... ol+history
If you need to to apply a previous version to the DB you can also use SQL Compare Pro (or SQL Data Compare, for static data)
http://documentation.red-gate.com/displ ... ic+version
Thank you,
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
Then, would I be correct that the corollary assertion to your answer vis a vis my question would be, "If one team member uses SQL Source Control then everyone must use SC because of locking." ?
Thanks again!
Multiple developers can use SQL Source Control.
The reason I mentioned SQL Compare is that it is a tool that can accomplish what you want and can work with scripts folders generated by SQL Source Control.
What do you mean by locking in this case? Are you referring to the object locking feature present in SQL Source Control?
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools