[AccessD] Access and SQL Server

Hi Gustav, Jim and All --

<<<
No considerations: Is this a tiny table? Or a lookup table only? Or?. 
Just do it, add the Id, and move on.
>>>
Yes.

As for performance issues for millions of rows as you Jim noted -  some very
small performance loss on inserting a row can be neglected.
Jim, let me suppose this my answer will be also an answer on two your other
today's postings here addressed to me?

2All: for the case of surrogate PK and a natural (compound) alternate key -
which one will you make based on a clustered index and which one - based on
non-clustered and why?


Thank you.

--
Shamil
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: 7 ????? 2011 ?. 18:18
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Access and SQL Server

Hi Jim

In, say, a grid you need to be able to identify any row quickly and easily
even if the table of this grid is the mother of all tables. 
Nothing beats an Id of autonumber in this respect: Always the same name,
same data type, same behaviour, same methods, same everything.

I realise it may require an index more, but that disadvantage is ignorable
compared to the huge advantages gained by a consistent use of an autonumber
Id for every table - which to me includes any lookup table as well. It makes
life safe and so much easier. No considerations: Is this a tiny table? Or a
lookup table only? Or?. Just do it, add the Id, and move on.

/gustav


>>> jimdettman at verizon.net 07-03-2011 15:29 >>>

I would not use an auto number as a key until I needed to use it as a FK
some where.