Subject | Re: Effect of GUID in primary key on v 1.5 vs 2.5 |
---|---|
Author | nathanelrick |
Post date | 2012-03-06T19:16:51Z |
why bigint ? you want to store more than 2.3 milliards row ?
integer = 4bytes
bigint = 8bytes
GUID = 16 bytes
and read just my previous article to understand that size of reccord are very important in speed (can be x10 to x100 more faster some case, but do some test)
integer = 4bytes
bigint = 8bytes
GUID = 16 bytes
and read just my previous article to understand that size of reccord are very important in speed (can be x10 to x100 more faster some case, but do some test)
--- In firebird-support@yahoogroups.com, "Eduardo A" <eas@...> wrote:
>
> Looking at creating a new database in a Win32 server that is expected to grow quite large and trying to decide whether to use GUIDs or BIGINT for the primary key. Will likely be using SuperServer architecture.
>
> Besides hosting local data at each server, some or all of the data in the new database may need to periodically be sent to a group or corporate server for further analysis and reports so GUIDs look attractive.
>
> Any significant difference in performance on GUIDs as primary keys in versions 1.5.6 and 2.5?
>
> Any significant difference in performance on GUIDs as primary keys in versions 2.5?
>
> Where can I find out more about whether it matters a lot if GUIDs are used as primary keys instead of the normal BIGINT sequences by generators?
>
> Which would be better?
>
> Thanks!
>
> -Eduardo
>