> why bigint ? you want to store more than 2.3 milliards row ?
>
> integer = 4bytes
> bigint = 8bytes
> GUID = 16 bytes

A BIGINT looks large, but once you work with dedicated PK value ranges
per site/server, I wouldn't go with an INTEGER.

Just a thought.

--
With regards,
Thomas Steinmaurer (^TS^)
Firebird Technology Evangelist

http://www.upscene.com/
http://www.firebirdsql.org/en/firebird-foundation/

> 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
>>
>
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>