Hello list, We are currently developing a large e-commerce site using SAPDB 7.4.3.27. We do expect to see a large number of inserts into the database, and are therefore considering how to assign key values for the inserted rows. Using a sequence is what we presently consider doing, as it has served us well in past, smaller implementations.
I see in the documentation that sequences can be created with maximum values up to 38 digits, but I have been unable to find any mention of any issues associated with using a single sequence for very high transaction volumes. I'd thus like to ask the list if there are any recommendations for the maximum number of transactions (nextval selects) per second (or other volume-based metric) a single sequence can support without having locking or other performance issues. Also, are there any changes in sequence performance in MaxDB 7.5 (and 7.6) compared to SAPDB 7.4? Thanks in advance for your insight! /Johan Hellgren -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
