Increase increment size to match GUID advantage
Posted
by TenaciousImpy
on Stack Overflow
See other posts from Stack Overflow
or by TenaciousImpy
Published on 2009-10-21T22:53:18Z
Indexed on
2010/05/20
20:30 UTC
Read the original article
Hit count: 306
Hi, I've been thinking of implementing this system, but can't help but feel there's a catch somewhere. One of the points of using GUID over incrementing int is that, in the future, if you were to merge databases together, you wouldn't have any clashes over the primary key/identifier. However, my approach is to set the increment size to X where X is the number of servers I'll most likely have in the future. Then, on each server, have the seed be an increment over the seed number on the previous server. That way, during merging, there would be no clashes with the primary key. Is this a safe, normal method or have I gone mental :)? Thanks
© Stack Overflow or respective owner