Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CLages
Posting Yak Master
116 Posts |
Posted - 2003-10-02 : 11:54:57
|
| Timestamp field writes the exacty moment when the record Inserted, Update, etc Right ?why when i use it, this fields does not start with the actual date.or in other words, is there a way to Set UP the start Timestamp field ? Carlos Lages |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-10-02 : 12:29:40
|
| A timestamp is not a datetime. It is a binary timestamp to be used to determine if the record has changed since the last time you looked at it.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-10-02 : 14:33:39
|
Timestamp is actually a misnomer. ROWVERSION is the appropriate name for the datatype. If you want to know when the row was created or last modified, I am afraid there is no shortcut: you'll need to do it yourself, by adding a datetime column to the table and populating it during the INSERT/UPDATE process. You could also use triggers for this purpose.Owais Make it idiot proof and someone will make a better idiot |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-02 : 14:42:15
|
quote: Originally posted by mohdowais Timestamp is actually a misnomer. ROWVERSION is the appropriate name for the datatype.
I read that Yukon will rename the datetype to ROWVERSION or something like that. So there shouldn't be anymore confusion in the next version at least.Tara |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-10-02 : 18:15:57
|
| It is RowVersion in SQL 2000. Timestamp is included for backward compatability. I doubt they would take that out and potentially break a lot of existing apps, but I guess it could happen.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
|
|
|