Comments
Sort by recent activity
By the way, the version of sql compare is 13.7 .4 and the version of sql source control is 7.0.11
/ comments
By the way, the version of sql compare is 13.7 .4 and the version of sql source control is 7.0.11
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. The weird thing is, my colleague add about 10 stored procedures. But only one of them was shown as dropped on get latest tab, the others are shown as new added on commit tab. / comments
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. ...
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. The weird thing is, my colleague add about 10 stored procedures. But only one of them was shown as dropped on get latest tab, the others are shown as new added on commit tab. / comments
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. ...
Hi @David Atkinson, Yes, we modify the same database. My procedures are always fine and my colleague's procedure mostly fine, sometimes it will show on get latest tab. For example, my colleague add 10 procedures, 9 of them will shown on commit tab, but 1 of them was shown on get latest tab. / comments
Hi @David Atkinson, Yes, we modify the same database. My procedures are always fine and my colleague's procedure mostly fine, sometimes it will show on get latest tab. For example, my...
David Atkinson said:
If you do a Git pull on your instance and refresh the vomit tab, does this help?
Actually my colleague did not use sql source control, I will add his stored procedure into git repository. So I almost don't need to use git pull feature. / comments
David Atkinson said:
If you do a Git pull on your instance and refresh the vomit tab, does this help?
Actually my colleague did not use sql source control, I will add his stored procedure in...
Hi @Tianjiao_Li , I encounter the same problem months ago and I
knew I can unlink and re-link the git repository to show the new added
stored procedure, I have done this operation months ago. Actually I
have no idea how to reproduce it.
Today I encounter the same problem again, I wonder if you can fix this. It's a little frustrated to do the boring operation.
/ comments
Hi @Tianjiao_Li , I encounter the same problem months ago and I
knew I can unlink and re-link the git repository to show the new added
stored procedure, I have done this operation months ago...
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. The weird thing is, my colleague add about 10 stored procedures. But only one of them was sh / comments
Hi @David Atkinson , We are using the shared model. The stored procedure was added by my colleague, it should shown as new added on commit tab,instead of shown as dropped on get latest tab. ...
Tianjiao_Li wrote: »
Hi @chuck ,
Thanks for your patience with this issue.
Unfortunately the development team hasn't been able to prioritise this work. Given the size of the backlog of higher-priority items, it doesn't look like it's something we will fix in the foreseeable future.
However we still have it logged as SC-9791 in our internal bug tracking system and we'll reassess it again in the future. Please keep an eye on the release note!
Understand, thanks. / comments
Tianjiao_Li wrote: »
Hi @chuck ,
Thanks for your patience with this issue.
Unfortunately the development team hasn't been able to prioritise this work. Given the size of the backlog of higher-p...
chuck said:
Tianjiao_Li wrote: »
Hi @chuck ,
Thanks for your patience with this issue.
Unfortunately the development team hasn't been able to prioritise this work. Given the size of the backlog of higher-priority items, it doesn't look like it's something we will fix in the foreseeable future.
However we still have it logged as SC-9791 in our internal bug tracking system and we'll reassess it again in the future. Please keep an eye on the release note!
Understand, thanks.
Hi, I found you fix this bug in this release version
13.3.6.6375 - June 4th 2018 SC-9791: The 'DROP and CREATE instead of ALTER' option is no longer ignored when creating a deployment script. / comments
chuck said:
Tianjiao_Li wrote: »
Hi @chuck ,
Thanks for your patience with this issue.
Unfortunately the development team hasn't been able to prioritise this work. Given the size of the b...
sam.blackburn wrote: »
SQL Compare 13.1 is currently only available on our frequent updates channel (although we expect to release it to everyone very soon). To get these updates sooner, you can turn on frequent updates as described here: https://documentation.red-gate.com/display/SC13/Turning+on+Frequent+Updates
Hi,
I want to know if you have fixed this problem, or you just designed it like this.(can not use drop and create when use git as source for sql compare) / comments
sam.blackburn wrote: »
SQL Compare 13.1 is currently only available on our frequent updates channel (although we expect to release it to everyone very soon). To get these updates sooner, you c...