.net transaction not able to select data

Question

0.00/5 (No votes)

See more:

Dear All,

I am back with one more problem today.

I have ADO.NET application which inserts data to table. (ex Invoices)

I have written Transaction with IsolationLevel.ReadUncommitted in my ADO.net Application using c# code

Whenever i run this application and try to select data from my Invoices table, i am not able to do so.

ex:
When i fire below query from my sql query window when ADO.net Application is running,
Below query works,
select * from Invoices with(nolock,nowait)

Below query does not work,
select * from invoices

I know that when we use with(nolock,nowait) we can read uncommitted data, but i want to read only committed data, but it seems that the transaction is putting lock on my table and not allowing me to read any data.

I want to read only committed data.

What I have tried:

I Tried IsolationLevel.ReadCommitted,IsolationLevel.ReadUnCommitted in my ado.net Application

Please suggest what can be done in this situation.

Posted 17-Aug-16 9:29am

sunil mali

Updated 25-Aug-16 1:57am

F-ES Sitecore

v2

Add a Solution

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)

The Praveen Singh · Answer 1 · 2016-08-25T01:57:00

OK, so the subject of SQL Server Isolation levels is quite a tricky one to get to grips with.
Now to address your question specifically, your SELECT statement cannot complete because it needs to read ALL records in the table and as the INSERT statement is still inserting records, the select cannot finish reading the table until after the insert completes.

Now let us suppose you are happy for your SELECT statement to ignore rows that are currently locked (i.e. those being inserted). You could use the READPAST query hint in order to permit your select statement to finish whilst the Insert statement is running.

SELECT * FROM TableName WTIH(READPAST)
Make sense?