Re: how do you handle multiple update request on the database?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Arne,

Try having more than 4-5 concurrent requests to an access database and
see what happens. It most definitely doesn't scale well.


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx

"Arne Vajhøj" <arne@xxxxxxxxxx> wrote in message
news:45ff22a6$0$90271$14726298@xxxxxxxxxxxxxxxxxx
Nicholas Paldino [.NET/C# MVP] wrote:
I made the assumption that the OP was using an RDBMS like SQL Server,
but the statement applies for any RDBMS. It will handle multiple update
requests that come in at the same time to the server. Things such as
Access,

Access should handle multiple updates fine. At least consistent.
Performance will not be good.

Any database will handle #2 fine. The OP wasn't clear about how he
wants sequential statements handled. If a database couldn't handle
sequential statements, then I would be pretty wary of it, wouldn't you?

??

It is basic knowledge that logic like:

x = SELECT MAX(id) FROM table
INSERT INTO table VALUES(x+1,'foobar')

is not generally safe.

Arne


.