May 14, 2009 at 11:31 pm
Hi,
our application is for taking online test (assessment). Here we have a requirement of around 10000 users to take test at once...
here the requests to database for storing data will be high....
This may lead to wait other requests for sometime...
Is there anyway to process these concurrent requests in a better way...? plz help me...
One more thing.. The data getting stored is very small xml of around five to six lines..
and only two or three tables used to store these data...
May 15, 2009 at 12:47 am
Hi,
Your just select (retrieve) the record? If so, then no need to think the concurrency just put the locks in the main table.
You need to stored the record with concurrency then
See this http://www.sqlservercentral.com/Forums/Topic717460-149-1.aspx#bm717601
ARUN SAS
May 15, 2009 at 1:01 am
Thanks Arun,
Here we are storing record everytime....
May be 2000 requests within 2 or 3 seconds...
May 15, 2009 at 1:05 am
Hi,
During sort, make sure no insert,update and delete operation happened in the main table the put the nolock in the main table
ARUN SAS
May 15, 2009 at 9:14 am
Hi
If your applications are primary inserting data you could create some staging tables which will be used by less users and use bulk operation to add the data into your main table.
Another approach is to split your main table into pieces.
Greets
Flo
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply