Posted - 01/31/2007 : 03:42:20
| Suppose I have a table called Account, Columns are:
AccountId, AccountBalance, UserId ........
And I have a batch application run at back-end to do:
list = get a user list;
foreach(user in list)
1,get all the accounts for the user
2,update accountBalance according to some logic (coule be 1 or 2 seconds)
commit or rollback
(this batch app proberbly use jdbc with default lock policy: READ_COMMITTED)
At the same time, I have web UI which could let user create account in account table.(only INSERT)
my question is:
if I want to create another account in web UI, is there any chance I will be locked (blocked) when the back-end app is running?
I've heard that INSERT and SELECT will not be blocked for the row level lock of sql server, but someone tell me sql server will do performance turning itself, so it will proberbly use a table level lock sometime.
All I want to make sure is if we can let the web user never feel blocked when he is creating an account.
it's hard for me to describe it well, but I really appreciate your helps!