>>>>
2. Stamp all transactions with the Server Date/Time OR >>>>
>>>>All, repeat,
ALL transactions should be written to the database using GETDATE from the server.
>>>>
>>>>Sure, you can post the local time as well (and 2008 has a new DateTimeOffset to deal with UTC), but every table should have a timestamp column for the server time - no exceptions.
>>>
>>>Because....?
>>
>>Because the server is where the data is and is the only constant. Workstations may have different times either because their clocks aren't synced with the server or because they are located in different time zones. But server time means something to the database itself and will not depend on who generated the timestamp.
>
>That I understand and agree with. What I was questioning was why every table should include a last-updated column.
Collision detection? Why shouldn't it? It is a timestamp, no? Based on datetime but not actually a datetime.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
