Comments
6 comments
-
Thanks for your post.
Would you be able to let me know what version of SQL Source Control you were using prior to your upgrade?
That may help me track down what's happened. -
Previously using 3.7.0.2
-
Thanks for your quick response, hopefully I'll be able to give you an update soon.
-
Incidentally, while we look into this, a slightly quicker way to get the revision rather than waiting for the history screen to load would be to right click your DB, select Properties, then Extended Properties. You'll see the revision listed there.
-
How do I get this revision number back?
-
Apologies for not updating everyone on this issue.
This issue was fixed in SQL Source Control 3.8.6, which was released to our Frequent Updates channel in mid-March.
If you'd like to know about about Frequent Updates, please see this thread.
The solution isn't available to users who only accept default channel updates yet, but it will be included in the next release.
Add comment
Please sign in to leave a comment.
Before upgrading we used to get the revision number right below the message with the "check mark" "Changes committed to source control".
Now this is missing.
We use this number to record in a document to move code.
We do have the revision in the db history in TFS, but this is an extra step to pull the version.
How do I get this revision number back?
Thanks,