> We have a considerable amount of data, and have not noticed any visible > speed issues with using GUID PK's in Firebird. Then again, we don't just > pull back 1 million records simply to find one record. We query only for > what we need - which greatly improves performance. And we use hard-coded > visitor of course. The benefits of GUID's also far outweigh the cons of > using other PK's types. > > I think today's databases are intelligent enough to correctly handle any > types of data (even if it is used for the PK or part of the PK).
HI, I am also worry about the performance but now not the select but insert. Since the way I generate the GUID like PK will not be sequentially increment to the last record. eg. last GUID PK for the new record will be 1BCF4-... now the new GUID PK may be 112N2-... next may be whatever, so it may lead to frequently index page split? ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
