SQL Server Update Lock Question

  • Can someone help me out. I currently have a stored procedure that is executed frequently to monitor the users session. The sproc validates the user based on a SessionID field which is a Unique Identifier. If the session exists in the table it then locks the table and updates a datetime field with the time it was validated. We are trying to re-design this process to use three tables instead of the one. Each table would have a unique check constraint on them so the data coming in would be written to one of the three tables based on the constraint. We would then place a view on the tables and update the datetime field through the view based on the sessionID.

    My question is would the update lock be placed at the table level or at the view level?

    If the lock is placed on the view I'm no better off then what I currently have.

    Any thoughts???

    Kevin

  • Unless you index the view it is not a 'physical' object, so the lock would be held on the table.

    ---------------------------------------------------------------------

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply