January 7, 2010 at 7:23 am
Comments posted to this topic are about the item SQL Script to check what was changed in database after 9PM Last night
January 18, 2010 at 12:46 am
I can't get this script to work on SQL server 2000, can you help? I get Invalid object name 'sys.objects'.
January 18, 2010 at 2:46 am
In SQL 2000 you'd use SYSOBJECTS; unfortunately the fields in the query aren't avialable in SQL 2000 so you'll need to wait until you've upgraded :sick:
If anbyone does know of something similar in SQL 2000 I would also be interested!
January 18, 2010 at 2:57 am
thanks for letting me know, regarding upgrading the server unfortunatly it's not an option for me
January 18, 2010 at 9:04 am
Nor me at present, but it's something to look forward to!
February 5, 2010 at 10:56 am
I think this script detects index rebuilds, which you might not always want. how can those changes be omitted ?
November 10, 2010 at 7:51 am
I think that Gary McGibbon might be onto something.
I ran the stored procedure against my production database, and it literally returned every user table in the database with sequential modify_date entries. It looks to me like either the nightly backup process, or the nightly UPDATE STATISTICS & REBUILD INDEX job caused it to return every table as being modified.
May 18, 2016 at 6:55 am
Thanks for the script.
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy