Comments
Sort by recent activity
Latest update. I decided to try a new, separate Subversion repository.
Unlinked the database from source control (Subversion).
Created a new Subversion repository.
Linked the database to the new repository.
Performed a Commit to push the initial checkin into Subversion.
Verified that "Get latest" had no updates.
Clicked on the "Commit" tab. My table is still in the list of changes that need to be commited ("Last changed by" is "unknown", not my name).
"Latest source control version" still shows TEXTIMAGE_ON [PRIMARY] at the end of the TABLE declaration as the lone difference.
If I pull updates from Subversion (we're using Tortoise SVN), the local copy of the .sql file does NOT contain "TEXTIMAGE_ON".
I tried clearing the local cache for SQL Source Control 5, but nothing changed.
Where is SQL Source Control getting this copy it's loading into the "Latest source control version" pane?
The 3 tables that were showing no changes before, are still showing no changes, but SQL Source Control wants to commit something (though this fails with "Nothing to commit" when I try). / comments
Latest update. I decided to try a new, separate Subversion repository.
Unlinked the database from source control (Subversion).
Created a new Subversion repository.
Linked the database to the new r...
After working with Support, my issues were related to a bug that was fixed in SQL Source Control 5.3.1.3378 / comments
After working with Support, my issues were related to a bug that was fixed in SQL Source Control 5.3.1.3378