Does SQL Source Control Object Locking impact non-Redgate users?

We would like to set up object locking on one of our development servers.  However, there are some developers on some of the databases on that server, who will not have Redgate tools installed.  Will there be any impact on these users, as long as we don't lock any objects in their databases?  Or can we set up object locking and they won't even notice anything has changed?
Tagged:

Best Answer

  • Alex BAlex B Posts: 1,052 Diamond 4
    Hi @Tim86,

    As long as you do not have those databases added to SQL Source Control (or do not lock objects in those databases if they are added to SQL Source Control) there will be no impact on users that do not have the tool installed.

    If you set up object locking and you lock an object, you will see a lock icon and get a message that the object is locked in SQL Source Control.  If you then try to modify that object (as a different user than locked the object) from a machine that does not have SQL Source Control installed, it will still fire the trigger and prompt you that the object is locked:
    Msg 50000, Level 16, State 1, Procedure RG_SQLSourceControl_DDLTrigger, Line 54

    SQL Source Control
    The object [database].[schema].[object] is locked by <user that locked the object>
    To unlock the object, in SQL Source Control, go to the Object Locking tab.
    I hope that helps!

    Kind regards,
    Alex
    Product Support Engineer | Redgate Software

    Have you visited our Help Center?

Answers

Sign In or Register to comment.