This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, i'm in the process of moving from Identity column key generation to KeyTable. The problem is, the value in KeyTable is just an int and it's very much expected that the database will contain millions of records at least in two tables. Won't the KeyTable method run out of keys? I've made some tests and with an IdentityBlockSize of 10 I've reached >4000 in a few seconds, so I'll reach the limits of the int type very quickly. Thanks. |
|
|
Hi, Best bet is to change the KeyTable to use a BigInt (or int64, or whatever your database of choice uses for 64bit integers). Then use that for your primary key fields. So if you change your database to use that for the keytable nextval type, and then update your entity identity type. There has been much discussion about how much data can be stored using that approach in this thread: http://www.mindscapehq.com/forums/Thread.aspx?ThreadID=2754 I hope that helps, John-Daniel Trask |
|
|
Oh, I hadn't realized you can change the key type just like that. Well, thank you, this answers my question.
|
|