sysobjects table question

[firsttube]

I want to create triggers on all the tables in a database that will update a date field in the sysobjects table with the current date anytime a record in any of the tables is updated.

My question is: is it recommended to alter the sysobjects table in any way?


Information is not Knowledge, Knowledge is not Wisdom, Wisdom is not Truth, Truth is not Beauty, Beauty is not Love, Love is not Music, Music is the best.

 

[AlexCuse]

I would create a copy of sysobjects and store your modified dates in there. I don't know if you would hurt anything by changing sysobjects, and I don't want to find out

Ignorance of certain subjects is a great part of wisdom

 

[bborissov]

As we said here "You play with the fire"
Don't mess with any of the system tables, views or anything stored in master table
Better create you own tracking table and store all you want there.

Borislav Borissov
VFP9 SP1, SQL Server 2000/2005.
MVP VFP

 

[ptheriault]

You should never, change system tables. You risk loosing changes with new service packs or new releases.

I would make a log table in the user database.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[firsttube]

I figured I should not touch those tables.

I made a copy of the table. Do I have to put triggers on all database objects that I want to be included in this tracking? Or is there a better way to do it?

Information is not Knowledge, Knowledge is not Wisdom, Wisdom is not Truth, Truth is not Beauty, Beauty is not Love, Love is not Music, Music is the best.

 

[AlexCuse]

Yes, you will need triggers on all objects. Or if updates are done through stored procs you can add the update of the date into your proc.

Ignorance of certain subjects is a great part of wisdom