Comments
Sort by recent activity
Actually, this is still an issue. We are looking to deploy changes to another database and when looking at the history through SQL Compare, the history window just sits there with the spinning green circle with the message "Waiting for other operations to complete". / comments
Actually, this is still an issue. We are looking to deploy changes to another database and when looking at the history through SQL Compare, the history window just sits there with the spinning gre...
Yes, this is the same machine. I tried to do a history in the vault client and found an issue with my local file storage. I resolved this issue but still have a problem with SQL Compare. I tried the compare against the local file store and it worked fine, so I expect that SQL Compare is having issues with Vault.
Additionally, if we simply do a compare to an "unchanged" database against the "head" revision of a branch in Vault, SQL Compare doesn't seem to pick up the need to use a migration script created through SQL Source Control, though we have created one. What, exactly, would cause SQL Compare to recognize that a migration script must be used and where to find it? / comments
Yes, this is the same machine. I tried to do a history in the vault client and found an issue with my local file storage. I resolved this issue but still have a problem with SQL Compare. I tried...
It appears that I have solved the issue. The fact that the error(s) were only occurring for me and the fact that an unlink/link did not solve it completely, I turned to Vault. It turns out that my Vault client cache was out of sync with the server. I cleared the vault client cache and now the problem is resolved.
Thanks for your guidance James; it helped me reach resolution. / comments
It appears that I have solved the issue. The fact that the error(s) were only occurring for me and the fact that an unlink/link did not solve it completely, I turned to Vault. It turns out that m...
The error is as follows:
Vault's cache hasn't been updated with the commit details
Expected 27953 actual 27954
.. and yes it gives me the option of submitting an error report to Red Gate. (Which I have done.) Note that after this I sometimes get a second error after waiting a long time for the Commit Changes tab to update. It seems to cycle through the 4 steps several times and then I get the error that indicates that the action failed after 5 tries, which also gives me the option to send the error to Red Gate. (Which I have also done.)
On the occasions where I get the second error, I have to unlink and relink the database to clear up the issue; which returns again once I commit changes.
Will provide results from other team members shortly. / comments
The error is as follows:
Vault's cache hasn't been updated with the commit details
Expected 27953 actual 27954
.. and yes it gives me the option of submitting an error report to Red Gate. (Whic...
Hmm...I had one of my co-workers attempt to make a change and commit it and they see no errors like I do. It appears to be an issue that only I am experiencing; which is odd because unlinking and relinking does not permanently resolving the issue. Is there something else I need to perform to clear out whatever settings SQL Source Control has for the database in question? / comments
Hmm...I had one of my co-workers attempt to make a change and commit it and they see no errors like I do. It appears to be an issue that only I am experiencing; which is odd because unlinking and ...
I did unlink and relink and that seemed to have resolve the issue temporarily. Now, whenever I commit changes, it appears that there is a disconnect between the version that SQL Source Control is expected and what our Vault repository is returned. It's expecting 2362 but 2363 was returned. (Numbers not actual, but vault is returning one version beyond what SSC is expecting.)
Now, after every commit changes, I have to unlink and relink to clear the issue.
I'll have to have another member of the team try to commit changes to see if similar issues are observed. / comments
I did unlink and relink and that seemed to have resolve the issue temporarily. Now, whenever I commit changes, it appears that there is a disconnect between the version that SQL Source Control is ...