What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI
COURSE of the MONTH
12 days, 7 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
MS SQL Server, multiple threads reading the same table
Posted on 2010-11-12
I want to have two threads reading from the same table with different queries. I use ADO with C++.
Will this work? Any special magic required?
Will this work? Any special magic required?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
5 Comments
Active 1 day ago
no magic required, this shall work.
of course, if you try to read (or update) the same records, you will get some "locks" (so your code will get into wait), but for the rest, nothing
of course, if you try to read (or update) the same records, you will get some "locks" (so your code will get into wait), but for the rest, nothing
You should use hints in your queries if you want sql to not lock records when selecting data. That is the default behavior of sql.
Use:
select yourselection from yourtable with(nolock)
if you want no data locked. You will, however, also be returned any dirty records. You can use
with(rowlock)
to only lock selected rows, or
with(readpast)
to not return any dirty rows.
Use:
select yourselection from yourtable with(nolock)
if you want no data locked. You will, however, also be returned any dirty records. You can use
with(rowlock)
to only lock selected rows, or
with(readpast)
to not return any dirty rows.
Active 1 day ago
>Why would two reads on the same record cause a lock?
it depends on which transactional level the 2 sessions are.
if the 2 are in serializable mode, everything they touch in common will make the other one to wait on that same resource... because further down the transaction, a update might occur etc...
for single queries, there is no issue, though, as you say, they just will issue a read shared lock, and can both continue without actually blocking each other
it depends on which transactional level the 2 sessions are.
if the 2 are in serializable mode, everything they touch in common will make the other one to wait on that same resource... because further down the transaction, a update might occur etc...
for single queries, there is no issue, though, as you say, they just will issue a read shared lock, and can both continue without actually blocking each other
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
In SQL Server, when rows are selected from a table, does it retrieve data in the order in which it is inserted? Many believe this is the case.
Let us try to examine for ourselves with an example.
To get started, use the following script, wh…
Occasionally there is a need to clean table columns, especially if you have inherited legacy data. There are obviously many ways to accomplish that, including elaborate UPDATE queries with anywhere from one to numerous REPLACE functions (even within…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
How to fix incompatible JVM issue while installing Eclipse
While installing Eclipse in windows, got one error like above and unable to proceed with the installation.
This video describes how to successfully install Eclipse.
How to solve incompa…
Suggested Courses
Course of the Month12 days, 7 hours left to enroll
777 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.