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 |
|
jfuex
Starting Member
29 Posts |
 Posted - 2008-07-18 : 11:21:12
|
| I am considering two architectures for an application where users will be doing data entry into a SQL database. In one data model, the data entry would involve a lot of new row INSERTs into a SQL table, and in the other proposal the same task would require UPDATEs of existing rows instead.I am trying to maximize the design for high concurrency and performance. Are there any performance/locking benefits to an INSERT model over an UPDATE model? Can SQL handle a lot of simultaneous INSERTs more efficiently than a similar number of updates on a single table?ooo Oooo O |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-07-18 : 12:30:05
|
| purely from a performance standpoint you're better off with inserts.since updates may split the pages which is an expensive operation.of course you have to have a unique ever increasing clustered index key like identity._______________________________________________Causing trouble since 1980Blog: http://weblogs.sqlteam.com/mladenpSpeed up SSMS development: www.ssmstoolspack.com <- version 1.0 out! |
 |
|
|
|
|
|
Insert versus update speed