Comments
Sort by recent activity
David Atkinson said:
@pablolerner - SSMS integration won't be in the first version although it's something that will be considered in future as we're aware of the convenience this brings. Regarding TFS integration, we're seeing the market move very swiftly away from TFVC and on to Git. Even Microsoft no longer recommend using TFVC, so I'd be curious to know if your organization have any plans to migrate? See the following article for more details.
Thanks David. The reason for staying in TFS is the same DROP_TABLE_Students mentioned: Source Control does not support the shared model for git. We need to stick to it since a databases bigger than 4 TB does not allow copies for every developer. But then, if the new tool does allow for the shared model with git we will be very happy to migrate. Integration with SSMS is not a must for us. But one question then. We currently use Source Control to commit to TFS and then SQL Compare to implement from TFS to the production environment. We don't care about repeatable migration scripts. Will we be able to stick to this procedure with the new tool? / comments
David Atkinson said:
@pablolerner - SSMS integration won't be in the first version although it's something that will be considered in future as we're aware of the convenience this brings.Rega...
Hello. We use Source Control with TFS as well. All databases set up as Shared. I have look at the video posted above but the process being described does not seem to work for my team. We can't go from Source Control already connected to TFS to two different tools, one for Database to folder versioning, and another (Visual Studio) for commiting changes into TFS. There are several members of my team who currently refuses to use Source Control due to the performance penalty in SSMS, I can't propose two tools as an alternative. The best scenario for us would be to have the same functionality that Source Control provides currently, but without the performance penalty in SSMS. / comments
Hello. We use Source Control with TFS as well. All databases set up as Shared. I have look at the video posted above but the process being described does not seem to work for my team. We can't go f...
ATurner said:
[...]you would have to commit with your preferred source control tool separately[...]
Hello. I don't know how much others will agree but this is not something that I, as a database developer and user of SQL Source Control, can call "suppor for Git". What you are describing is just support for script files in the file system and then using Git as a completley sepparate tool. What I need, and please I ask the other users in this thread to clarify if they do too, is for SQL Source Control to provide all the functionality within it self, without using external tools. By the way, going back to my original question in this thread, I was never able to make this work for me.
/ comments
ATurner said:
[...]you would have to commit with your preferred source control tool separately[...]
Hello. I don't know how much others will agree but this is not something that I, as a data...
Thanks for the answer. / comments
Thanks for the answer.
Thanks for the answer. / comments
Thanks for the answer.
I see... well I will try to test it. thanks / comments
I see... well I will try to test it. thanks
Well, it does not look like the scripts folder will work for me since I still need to upload SQL objects to Team Foundations Server. So, I will be using ADS to develop, then SQL Compare to generate scripts and then need to open some other application to commit those scripts to TFS, maybe SSMS? That is too many steps. It is best if I just stick to our current model to use SSMS with Red Gate's Source Control. It is easier. And, when the new stand alone version of Red Gate's Source Control becomes available I will see my options. Thanks.
/ comments
Well, it does not look like the scripts folder will work for me since I still need to upload SQL objects to Team Foundations Server. So, I will be using ADS to develop, then SQL Compare to generate...
oh, no. I have tryed setting "Source Control" as the target.
We usually set "Source Control" as the source and our production database as the target. That is how we implement changes in our production environment.
[image]
/ comments
oh, no. I have tryed setting "Source Control" as the target.
We usually set "Source Control" as the source and our production database as the target. That is how we implement changes in our produc...
wow, well, thanks, this is great, but unfortunatelly we are not using Git, we are on Team Foundation Server. And I have tryed with SQL Compare setting my development DB as source and Team Foundation as target and it does not work since it forces to just create a script, and then I have to still use SSMS to upload it to Team Foundation. / comments
wow, well, thanks, this is great, but unfortunatelly we are not using Git, we are on Team Foundation Server. And I have tryed with SQL Compare setting my development DB as source and Team Foundatio...
Thanks. / comments
Thanks.