Stupid question re adding rows

ryetee

Registered User.
Local time
Today, 06:18
Joined
Jul 30, 2013
Messages
952
Without specifically having a date/time stamp on a table is there anyway in working out (from ystem tables maybe) when a row was added to a table?
 
Not exactly. You can run this query to see when a table was last updated:

Code:
SELECT NAME, DATEUPDATE FROM MSYSOBJECTS

It doesn't tell you what was updated/added/deleted, just when the last one occured.

On a side note, god love Microsoft for using a reserved word as a field name in a system table. Expect nothing less.
 
Not exactly. You can run this query to see when a table was last updated:

Code:
SELECT NAME, DATEUPDATE FROM MSYSOBJECTS

It doesn't tell you what was updated/added/deleted, just when the last one occured.

On a side note, god love Microsoft for using a reserved word as a field name in a system table. Expect nothing less.

Unfortunately does't help!
My own stupid fault really, should have realised I would need it one day!
 
you never miss it until you need it!

If you don't have it already, also include a field for who updated/appended and where from if appropriate so you have the full story e.g.

appended by xxx on xxx date from a file called xxxx
manually appended by yyy on xyz date
updated by xxx on xxx from a file called zzzz

sometimes easier to keep the data in a log file - depends on the application
 
you never miss it until you need it!

If you don't have it already, also include a field for who updated/appended and where from if appropriate so you have the full story e.g.

appended by xxx on xxx date from a file called xxxx
manually appended by yyy on xyz date
updated by xxx on xxx from a file called zzzz

sometimes easier to keep the data in a log file - depends on the application

I do have some tables with a "when updated". I also have some tables with a field stating who did it. I have other tables with bith!! However these were done with specific things in mind.It sounds like a great idea to keep track of updates/appends as you've pointed out- it would have made debugging a prod problem so much easier. I'm guessing at the moment what has happened. Pretty sure I'm right but can only prove 99% of it and my OCD won't let it go!
 
just a suggestion - if you have regular backups you can create a quasi date by comparing backups with the current record using the data of the backup as the quasi date
 
just a suggestion - if you have regular backups you can create a quasi date by comparing backups with the current record using the data of the backup as the quasi date

Am trying that but I only keep 4 backups which could span a few weeks or as I suspect 4 days which won't be enough
 

Users who are viewing this thread

Back
Top Bottom