> Not that MAX() is perfect. In very-high-insert environments people
> sometimes generate random ID's, catching and trying again the few
> that collide with existing values; the theory is that the insert
> activity is then spread around the table (physically), avoiding a
> "hot spot" with lots of write contention. May only work in
> multiprocessor DBMS systems.
You can get the same effect by placing the clustered index on a field other
than the identity column, which gives you the added benefit of very fast
string searches against that column if it's a string datatype.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
