Activity overview
Latest activity by deebo
There is an opportunity cost to be acknowledged with this, which is all I'm getting at. I am the nominal "IT" staff in support of an engineering group. You may be 100% technically correct in the need for VCS but there is an interpersonal aspect to everything. Showing up and telling them they have the wrong idea and need to wake up is not really going to fly. / comments
There is an opportunity cost to be acknowledged with this, which is all I'm getting at. I am the nominal "IT" staff in support of an engineering group. You may be 100% technically correct in the ne...
Not impossible. I just need to be able to make the case for:
1. making database structure/ data management changes
2. users adopting (and getting trained up in) github/SourceTree/SourceControl/general version control philosophy
I'm not the DBA so I don't have the keys to the castle and yet #1 is still the easiest. The existing model (or lack thereof) is completely open access editing to a single development database. We only have a few editors but we want to get away from this for probably obvious reasons. However, any time a "thou shalt" is handed down from above and it makes a users life harder in the short term there is going to be some level of pushback, at least in my environment. Currently they make an edit and hit run. If we adopt this there are going to be a half dozen more hoops to jump through. I need to be able make a strong case for why the change is beneficial.
I hope that helps.
Thanks again! / comments
Not impossible. I just need to be able to make the case for:
1. making database structure/ data management changes
2. users adopting (and getting trained up in) github/SourceTree/SourceControl/gene...
Right now I'm doing a proof of concept so I'm testing out a variety of setups that might work with our existing software constraints. Our current setup does not allow for the dedicated model but it is looking like that would be the way to go in the future, especially if we're branching.
As for the branching, you are correct. If I switch branches in SourceTree then it will be reflected automatically in SSMS/Source Control. I did not notice how Source Control tells you the branch it is looking at in the top right until just now. However, the only way I was able to get this change to show was to close and restart SSMS. No amount of waiting/ refreshing would do it, which is unfortunate.
Thanks for the response Alex. This helps to put me on the right track. / comments
Right now I'm doing a proof of concept so I'm testing out a variety of setups that might work with our existing software constraints. Our current setup does not allow for the dedicated model but it...
how to manage branches?
Hello,
Apologies if this is a remedial question but I'm having a hard time understanding the branching process when working with Source Control. I've read the online docs and the main piece I'm not...