Select update not reserving data

Question

0.00/5 (No votes)

See more:

Dears,

My SQL Server procedure selecting and updating data and many source trigering same procedure and sometime same row updating from several sources, does it have any way how to reserve data for updating only from one source?

What I have tried:

select update but its not helped

Posted 31-Aug-20 5:37am

kgulboev

Updated 31-Aug-20 5:59am

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)

Wendelius · Answer 1 · 2020-08-31T05:59:00

One way is to use SELECT FOR UPDATE structure to lock the records during the select and release the locks upon COMMIT or ROLLBACK. For more information, see MySQL :: MySQL 8.0 Reference Manual :: 15.7.2.4 Locking Reads[^]

If you need to extend the control outside the boundaries of a transaction you can use TIMESTAMP data type to implement optimistic concurrency control. About TIMESTAMP see MySQL :: MySQL 8.0 Reference Manual :: 11.2.2 The DATE, DATETIME, and TIMESTAMP Types[^]

For an example of optimistic concurrency you can refer to How to Prevent When a Transaction Accidentally Overwrites Modified Data[^]. Even though the article is written for SQL Server, the principle is the same.

EDIT
Looking at the question again I felt unsure if you're using MySQL or SQL Server. If you're using Microsoft SQL Server, you can lock the records you select for example using WITH UPDLOCK hint in your query to ensure that the records are locked regardless of the concurrency settings. See Table Hints (Transact-SQL) - SQL Server | Microsoft Docs[^]

And in case of SQL Server the article should be accurate.