Posted by --CELKO-- on 10/08/05 19:03

The short answer is "No", it makes the table bigger and size will slow
down operations (probably not by much, but some).

The right answer is first, get the logical design right. An IDENTITY
cannot ever be a logical key, so is this thing actually a table at all?
What would the TIMESTAMP mean in your data model?

• Next in forum: Schema Diff Tool
• Prev in forum: Re: SQL for field names from a table
• Thread view: Re: PK and Timestamp in same table?

[Reply to this message]