Settings and activity

1 result found

1. SVN Lock mode by default : Impossible to commit

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  SQL Source Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   AdminRedgate Administrator (Admin, Redgate) responded

   We currently do not support lock or exclusive checkouts (lock-modify-unlock model). We are supporting a copy-modify-merge model.

   In order to use SQL Source Control, you’ll need to use this model for now until we implement locking/exclusive checkouts in a future release.

   To do this, undo the change to the Subversion configuration file, remove the needs-lock property from any file in the repository, manually svn update the WorkingBases directory, unlink and then relink the db in SSMS.

   Depending on your OS, related files can be found in:
   C:\Documents and Settings\\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
   or
   C:\Users\\AppData\Local\Red Gate\Logs\SQL Source Control 0

   1) Right click on WorkingBases\\Stored Procedures\dbo.PS_select.sql
   and select Properties
   *You can find the which corresponds to your db by looking in the LinkedDatabases.xml file.
   2) Select the “Subversion” tab at the top
   3) Click the “Properties…” button near the bottom
   4) Is there a svn:needs-lock property? If so, remove it.
   5) Click OK to close the SVN properties window
   6) Click OK to close the file properties window
   7) Right click again and commit the change to Subversion (this is just committing the change that a lock is not needed on that file)

   Now, you should be able to commit the file from SQL Source Control with out getting this permission error. Please let us know if you still have any problems.

   We currently do not support lock or exclusive checkouts (lock-modify-unlock model). We are supporting a copy-modify-merge model.

   In order to use SQL Source Control, you’ll need to use this model for now until we implement locking/exclusive checkouts in a future release.

   To do this, undo the change to the Subversion configuration file, remove the needs-lock property from any file in the repository, manually svn update the WorkingBases directory, unlink and then relink the db in SSMS.

   Depending on your OS, related files can be found in:
   C:\Documents and Settings\\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
   or
   C:\Users\\AppData\Local\Red Gate\Logs\SQL Source Control 0

   1) Right click on WorkingBases\\Stored Procedures\dbo.PS_select.sql
   and select Properties
   *You can find the which corresponds to your db by looking in the LinkedDatabases.xml file.
   2) Select the “Subversion” tab at the top
   3) Click the “Properties…” button near the bottom
   4) Is there a svn:needs-lock property?… more

   anonymous shared this idea  ·  Apr 22, 2010