Bug: committed objects not listed
I added some stored procs on the main repository. They're in the SVN repository fine, but when I go to a slave system and choose Get Latest, those objects are not created or listed in ). When I go to Commit Changes I get told to drop those objects!
I can't find any way to say that the repository is correct and the slave should be updated.
Note that this is a completely fresh slave, created five minutes ago with just the initial checkout, no edits.
Closing for now, since this can’t be reproduced. Please let us know if you hit this issue again. Thank you!
-
lakeland commented
Another follow-up... I had a good go at reproducing this today and failed.
-
This is very strange. The steps to reproduce are exactly what you should be doing. This makes me think that there is something specific about that db or the source control repository that it is linked to.
Do you have another db that you could try to source control? Does this problem occur with every db?
Do you have SQL Compare? Would you be able to compare the db to a snapshot and create a new snapshot that you could email to SqlSourceControlSupport@red-gate.com? Also email us the files that are in in source control. This will only be used internally to try and replicate and fix your issue.
If not, I hope you could try the following steps. If you have the problem again, then you could email SqlSourceControlSupport@red-gate.com the latest log file, which can be found at C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
or
C:\Users\<username>\AppData\Local\Red Gate\Logs\SQL Source Control 0.PreReqs) DB1 not linked to source control
1) Select DB1 in the Object Explorer
2) Right-click and select "Link to source control..."
3) On the setup tab, click "Create a new link to source control..."
4) Enter the URL to an empty directory in SVN (This should be a completely new folder in source control, which you'll have to create using TSVN or SVN first.) and click the "Create Link" button.
4a) After the linking completes, right-click on the URL on the Setup tab and copy this for later.
5) Click on the Commit tab at the top
6) Enter a comment
7) Click the "Commit" button8) In SSMS Object Explorer, right click databases and select "New Database..." and create a new db. We'll call this DB2
9) Refresh the Object Explorer so that the new db appears in the Databases hierarchy
10) Select DB2 in the Object Explorer
11) Right-click and select "Link to source control..."
12) On the setup tab, click "Link to an existing..."
13) Paste the URL copied above and click the "Link" button
14) Click on the "Get Latest" tab at the top
15) Click the "Get Latest" button -
lakeland commented
Further comment - I'm still getting this error so if there's anything extra I can provide then I'd love to know...
Steps to reproduce:
1) Create a new database
2) Link the new database to version control
3) Update the new database using SQL Source Control
4) Note errors... -
lakeland commented
Followup - I have used 'undo changes' to revert all but one of the missing objects.