October 5, 2006 at 2:36 pm
Which is better for concurrency, non escalating lock and data integrity RowLock or UPDLOCK.
environment high transaction volume(1000/per min) (for Inserts, Updates and selects)
updating/selecting in most cases one or several records and inserting a record to different tables.
October 7, 2006 at 6:16 pm
For what? Inserts, Updates, Deletes, or Selects?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:00 am
note that technically a select is not a transaction as it doesn't change data. Umm 1000 transactions/min ( did you mean minute? ) is not even low volume really and certainly not high!.
On the other side of the counter, poor code/design/strategy at 2 transactions/sec can seriously screw your server, whereas a good setup may run at several k on the same hardware etc. etc.
As Jeff says, for what and why? do you have a problem?
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
October 12, 2006 at 7:29 am
Yeah.. that's what I was kinda getting at... if it's all SELECTs, what's the problem
Also, what I've found is that a lot of folks use a transaction table also as a batch table and wonder why the world freezes why they do major processing on the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply