My asp.net application uses some sequences to generate table primary keys. Db administrators set the cache size to 20. Now the application is tested, and several entries are added every day (say 4 for each user test session). I found that new entries in the test session always use new parts of the cache, as if the timeout for the cached numbers expired, losing a tenth of the keys every day. I would like to understand if this is due to some kind of error that I could make in my application (utilization of tables or some other), or if this is the usual behavior. Are there any better programming methods to consider when working with oracle sequences?
Since the application does not have to carry a heavy load on the work (say, 20-40 new entries per day), I paid attention if this could be the case to set a smaller cache size or nothing at all. Does resizing a sequence cache mean resetting the current index?
in advance for any hint
user260192
source
share