Drop Table
Support Forum for database administrators and web based access to important newsgroups related to databasesHi, I'm perplexed by the large amount of lock activity in our SQL Server 2000 sp3 system. Thousands of requests per second with only a handful of users touching less than 30 tables. In trying to understand this, I running a simple select query with the NOLOCK hint. In Profiler, I see a number of Lock:Acquired events occuring. This surprises me as I thought this hint woul d not request nor consider locks. Any insight to this would be very much appreciated, as well as an opinion if this should be a performance concern, which is where I'm coming from. Many Thanks, Reuven
Post Follow-up to this messageCheck the DatabaseID,Mode and ObjectID. You'll see that 99% of them are hitting system objects - this is normal behaviour. The only locks you should see on your table accessed with nolock are Schema Stability (and possibly Compile) table level locks. You can check the "Exclude system IDs" checkbox on the Filters tab in Profiler to cut down the noise of the system objects. -- HTH Jasper Smith (SQL Server MVP) http://www.sqldbatips.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "ReuvenT" <ReuvenT@discussions.microsoft.com> wrote in message news:99AA5475-9887-4733-8AB7- D466B222A60E@microso ft.com... > Hi, > I'm perplexed by the large amount of lock activity in our SQL Server 2000 > sp3 system. Thousands of requests per second with only a handful of users > touching less than 30 tables. In trying to understand this, I running a > simple select query with the NOLOCK hint. In Profiler, I see a number of > Lock:Acquired events occuring. This surprises me as I thought this hint > would > not request nor consider locks. Any insight to this would be very much > appreciated, as well as an opinion if this should be a performance > concern, > which is where I'm coming from. > > Many Thanks, > Reuven
Post Follow-up to this messageThanks for the suggestion and info - very helpful. Reuven "Jasper Smith" wrote: > Check the DatabaseID,Mode and ObjectID. You'll see that 99% of them are > hitting system objects - this is normal behaviour. The only locks you shou ld > see on your table accessed with nolock are Schema Stability (and possibly > Compile) table level locks. You can check the "Exclude system IDs" checkbo x > on the Filters tab in Profiler to cut down the noise of the system objects . > > -- > HTH > > Jasper Smith (SQL Server MVP) > http://www.sqldbatips.com > I support PASS - the definitive, global > community for SQL Server professionals - > http://www.sqlpass.org > > "ReuvenT" <ReuvenT@discussions.microsoft.com> wrote in message > news:99AA5475-9887-4733-8AB7- D466B222A60E@microso ft.com... > > >
Post Follow-up to this message
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread