Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
harshal_in
Aged Yak Warrior
633 Posts |
 Posted - 2002-12-09 : 23:56:21
|
| I have a table which at times is can be updated by a thousand users at a time through a web page.the table is going to be updated at the same instance,will all the inserts succeed ? do i have to do anything or the internal system will take care of the locking on the table? and there is a timestamp column in the table which has the default as getdate() to capture the current time,so what will be the difference between the first and the last entries if the insert is concurrent?help appreciated.harshal. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-12-10 : 05:48:06
|
| sql server only holds times to a granularity of a few milliseconds so you can get several inserts/updates with the same time.If you want to give some sort of ordering to this then use a timestamp column (not the same as a datetime default getdate()).updates/inserts will usually succeed but will be queued by the locking mechanism. Beware of deadlocks though.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
harshal_in
Aged Yak Warrior
633 Posts |
Posted - 2002-12-10 : 05:55:41
|
| ok thnxs |
|
|
|
|
|
|
concurrency control