customer number or order number....we in theory should/could still be using
UUID() for future growth potential...does that make sense, a UUID as the PK
and still use the autoid int field...spose it doesn't matter....is that how
y'all handle it?
Regards,
Eric
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man."
-- George Bernard Shaw
_____
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 10:02 PM
To: CF-Talk
and in doing this, even with a large table, you find no performance hit
on sql server indexing that column and/or query on that table and using
that column in the where clause?
tony
-----Original Message-----
From: Stacy Young [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 10:51 PM
To: CF-Talk
Subject: RE: Primary key preference quick poll
I've begun to use UUIDs much more often these days...
Stace
_____
From: Michael T. Tangorre [mailto:[EMAIL PROTECTED]
Sent: November 10, 2003 10:43 PM
To: CF-Talk
Subject: RE: Primary key preference quick poll
UUIDs
Unless your database is going to house a terabyte worth of info, the
perofrmance hit is negligable and you will be all set for merges in
replication, easier time porting to different platform, etc...
I have never been a big fan of identities and have never worked with any
DBAs who have been. This topic has been discussed before, lets not blow
it
out of the water again.. search the archives.
_____
From: Sutton Yamanashi [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 9:09 PM
To: CF-Talk
Subject: Primary key preference quick poll
Why do you prefer
1. int (Identity / auto_increment)
2. char maybe with CreateUUID()
3. varchar
other?
Thanks!
-sutton
_____
_____
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
