Andrew Piskorski said: > No. Sequences in an RDBMS are designed to scale gracefully under > heavy concurrent load. (This is basic stuff, grab any good I think Mark was talking about my Sybase solution (sequence table) for if you don't want to use "identity" columns.
> I think SQL Server and Sybase use auto-incrementing column values, for > example. Yeah they do. They have a bit of a bad rep, though. Do a google on "sybase identity gap" to see what I mean. That and they require extra work if you want to transfer a table from one DB to another, but not much. > And of course, serializing all writes (or even all transactions > period) works just fine if your load is moderate and your application The load can even be pretty high. Unless you are doing an amazing amount of inserts, it's not going to matter, especially if you first get the sequence in a different transaction. Cheers, Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
