- A developer is working with a database in dedicated mode using SSC version 126.96.36.199.
They make changes to the database and commit them to our SVN repository.
The production database backup is then restored to the server that developer is using overtop of the database they've modified.
When they check the Get Latest tab it does not show the change they added to the SVN repository even though their change is not in the database.
In their working base directory for that server, there is a copy of the SQL file that matches the SVN repository (which is why I'm guessing the Get Latest tab is not showing it as a difference).
Currently, we unlink the database and then link it again. This seems to create a new working folder and generate a new compare. Is there are way for us to tell SSC to rebuild the working base, or force it to update w/o unlinking and re-linking?