Alternative solution of NOLOCK

Question

0.00/5 (No votes)

See more:

Hi CodeProject,

We are facing an issue in our application ; that in many procedures SELECT Query is written without NOLOCKS which is creating too much problem of PERFORMANCE.

Please suggest some alternative so that we can go AHEAD for improving the Performance of Application (EXCEPT INDEXING) ; without going for altering in each procedure and replacing all SELECT with SELECT NOLOCK statement.

Thanks,
Nitish Srivastava

[edit]SHOUTING removed - OriginalGriff[/edit]

Posted 20-Jan-15 20:09pm

NitishIgate

Updated 20-Jan-15 21:40pm

OriginalGriff

v2

Add a Solution

Comments

Tomas Takac 21-Jan-15 2:54am

What kind of performance problems? I don't think there is a magical switch that would solve your problems. You have to go trough all of them and solve one by one.

NitishIgate 21-Jan-15 10:59am

While Fetching the data from the table ; and processing them with many inner join(s) creating delays of Operation(s). Indexing and Optimised query is helping. But can we have some other think over the performnace ?

OriginalGriff 21-Jan-15 3:40am

DON'T SHOUT. Using all capitals is considered shouting on the internet, and rude (using all lower case is considered childish). Use proper capitalization if you want to be taken seriously.

Kornfeld Eliyahu Peter 21-Jan-15 4:05am

Lock for itself is not a performance issue, on the other hand run anything with NOLOCK can create other problems of concurrent use...
So to help you, you must be much more specific about your exact problem...

Sumit Jawale 21-Jan-15 4:06am

your PERFORMANCE is not depend on NOLOCK.. Please try to optimise your query.. There are so many ways to optimise it..

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sisir Patro · Accepted Answer · 2015-01-20T22:03:00

Hi,

From your question I can only figureout that your query is having some performance issues. You can optimize the query for increasing your performance of website.

As per my knowledge NOLOCK will only be used on a table if there is a frequent insert, update and delete operation simultaneously on the same table of data.

If your database tables are not having frequent insert, update or delete operations then you need not to use NOLOCK concept in your database query. The only thing you need to pay attention is your query should be optimized and take less time to execute.

Thanks
Sisir Patro