PiMané (10/21/2013)
There's a bad way to accomplish that..Just use XLOCK... XLOCK makes an exclusive lock to the record until the transaction is committed...
On c# you can:
1. begin transaction
2. SELECT 1 FROM tableToLock WITH (XLOCK) WHERE Id = @ID
3. do what ever you want....
4. commit transaction
But it's a risky thing to do...
Pedro
Sounds like you want to open a transaction when you read the record for update in the web form? Then keep that transaction open until the web form saves? What happens if they close the browser without saving?
Not sure how advisable that is.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St