I would absolutely agree with Brian on both points. I've stored SQLServer
GUID's in VARCHAR2(36) column previously...no issues. The dashes are kind
of wasted space...you could strip those out and store them in VARCHAR2(32),
which is what I normally use for Oracle SYS_GUID's. I also agree that there
will be a performance hit, but it will be negligible. If it's a huge
database (like in mult-terabyte), storage might be a concern...
"Brian Peasland" <dba_at_remove_spam.peasland.com> wrote in message
news:4069B869.FFD1846D_at_remove_spam.peasland.com...
> > How about the performance when using a string as Primary key - is
there
> > any significant difference compared to using a number?
>
>
> It has been my experience that any performance differences are
> insignificant. One could make a case that a large string will take more
> room to store than a number, therefore limiting the number of entries in
> an index's leaf nodes and this can contribute to a performance
> difference. But this will most likely be inconsequential.
>
>
> HTH,
> Brian
>
>
> --
> ===================================================================
>
> Brian Peasland
> dba_at_remove_spam.peasland.com
>
> Remove the "remove_spam." from the email address to email me.
>
>
> "I can give it to you cheap, quick, and good. Now pick two out of
> the three"
Received on Wed Mar 31 2004 - 19:49:17 CST
