>Sometimes I want that, sometimes I don't. I don't see it as a hard and fast rule, which is the way you stated it.
>
>So you design a database "solely" based on what "you" want? <s>
>
>Run this by a DBA....EVERY table should have a way to uniquely identify a single row, and EVERY table needs a timestamp column generated by the server. Period.

I agree completely that you need a way to uniquely identify a row. I *always* use an identity column as the primary key of all of my tables (SQL server is always my data store).

I'm not so sure about a timestamp column on every table. I'd certainly say most tables should have one (especially if the data is user entered - in that case then userID is a requirement also IMHO). Some reference tables just don't have that need IMO.