do not set any locking\blocking

Question

do not set any locking\blocking

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

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Mad-Dog (7/31/2016)
table scan is not good because some tables can have even millions rows for they temp table.

I didn't say it will cause table *scans*. Setting those options to false means the locks SQL is allowed to take are table *locks*

what i can set to false that will reduce the locking and wouldn't do table scan?

GilaMonster (5/27/2016)
Have you tried read committed snapshot? Won't help with deletes blocking inserts, but will help with reads.
And have you checked the indexing to make sure it supports the queries? Poor indexing often results in blocking problems.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jeff Moden SSC Guru Points: 1004403 More actions · Answer 2

Mad-Dog (7/31/2016)
they know about the problem and for now they can't fix the problem.
table scan is not good because some tables can have even millions rows for they temp table.
what i can set to false that will reduce the locking and wouldn't do table scan?
Thanks

Do you know what the problems are? Have you done an analysis to find the "bad" queries and see if a proper index might fix them?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)