Comments
Sort by recent activity
Thanks David,
Okay; that confirms for me that the cross branch migration script won't work, and I understand why. We'll be looking forward to this being supported at some point in the future.
For now, I think we can "cheat" by resetting the version extended property to the version that the development branch started with, or removing it entirely, which seems to work. / comments
Thanks David,
Okay; that confirms for me that the cross branch migration script won't work, and I understand why. We'll be looking forward to this being supported at some point in the future.
For ...
Thanks for clarifying David.
Our situation is that we have a Production branch that reflects what we currently have in production and we branch from that to create a development branch when we begin working on a new release. During development we use a development database linked to the development branch. Since our development may take some time, we could have some changes required to our production database that must go into production before the release will. As a result, the production branch has progressed at the same time as the development branch. (This could also happen if we had two distinct releases in development at the same time.) Either way we need to resolve this. Typically we would make the same change to the development branch that we applied to the production branch. This is very common for us.
Ultimately, when development is complete and we are ready to deploy we could take one of two approaches:
1. Using the source control tool (vault in our case), merge the development branch to the production branch and then deploy to the production server from the production branch -OR-
2. Deploy to the production server from the development branch and then subsequently bring the changes into the production branch either through merge or through linking in SQL Source Control and committing changes.
This is our first time working with SQL Source Control so it is entirely possible that we are trying to use the tool incorrectly or in a way that was not intended or thought of. / comments
Thanks for clarifying David.
Our situation is that we have a Production branch that reflects what we currently have in production and we branch from that to create a development branch when we begi...
We are having similar issues with items like Show History and just trying to see the Commit Changes tab. Sometimes we get errors, which I've sent to Red Gate using the automated process, but have not heard anything back yet. / comments
We are having similar issues with items like Show History and just trying to see the Commit Changes tab. Sometimes we get errors, which I've sent to Red Gate using the automated process, but have ...
Wait, I apologize, we were choosing the source control location incorrectly when SQL Compare did not recognize the need for a migration script. We figured that out. Again, sorry about the additional question. / comments
Wait, I apologize, we were choosing the source control location incorrectly when SQL Compare did not recognize the need for a migration script. We figured that out. Again, sorry about the additio...
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 ...