Home Forums SQL Server 2016 SQL Server 2016 - Development and T-SQL Is there a row locking similar to Oracle's row locking in SQL SERVER 2016 RE: Is there a row locking similar to Oracle's row locking in SQL SERVER 2016

  • February 23, 2018 at 6:35 am

    #1980912

    andrew gothard - Friday, February 23, 2018 3:13 AM

    Hi,
        personally, this question is one which (possibly wrongly) suggests a probable underlying design issue to me.  Would you be able to describe your problem a little more fully?  What format are your identifiers taking - how are they calculated, for example, what datatype(s) are they? 
        In general, manual row locking is very much a 'best avoided' process.  I have seen this approach cause significant bottlenecks in not enormously busy systems for a start

    cheers
    Andrew

    I agree... intentional row locking is a good way to create a problem, and NOT a good way to solve one.   I have to wonder why a sequence isn't being used.   Oracle has had them available for a rather long time, and SQL Server has had them since SQL 2014.   They usually get used to help solve these kinds of problems.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)