Force "Get Latest" even when tool thinks there are no changes.
Our test environment is set up such that the servers and databases all have the same name as production. This causes SQL Source Control to think I'm connected to ServerA when I am really connected to ServerB. Thus, the "Get Latest" tab shows "No new changes in source control" even though there are changes I wish to get. The "Commit Changes" tab still shows changes so the tool knows there are differences, but won't show any "Get Latest" items. This happens in both the "Dedicated" and "Shared" setups. I must unlink the database and relink it in order for it to work.
I would like to be able to FORCE a "Get Latest" so I can pull down the code from TFS (source control) in this situation.
Considering that the "lab environments match production environment" method is pretty standard these days it is hard to imagine other folks don't also have this problem. But I guess the votes don't lie. I may consider bribing for votes! hehe.
Chris Hearson commented
+1 from me. Force Get Latest is a basic SCC feature, supported in tools like TFS and others, so why not in SSC?
The server names are the same, the instance names are the same, the database names are the same; but they are in different fenced environments and each has a different IP. For example:
ServerA = 10.1.1.0 = Test environment
ServerA = 10.2.2.0 = Integration environment
ServerA = 10.3.3.0 = Production
Then, in our "hosts" file, we have this entry:
That way, in SSMS (and other tools), I just connect to "ServerA.test", "ServerA.int", or "ServerA.prod" depending on which environment I need to hit. This thread may help, too - http://www.red-gate.com/MessageBoard/viewtopic.php?t=13026
Does that answer your question?
Is the full path to the server the different between dev and test, when you include domain?
e.g. Is one database on
and the other one
or do you connect to them with exactly the same Server and Instance name?