|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, April 15, 2011 10:48 AM
Points: 250,
Visits: 55
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 12:15 AM
Points: 244,
Visits: 300
|
|
| I can't get this script to work on SQL server 2000, can you help? I get Invalid object name 'sys.objects'.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 3:29 AM
Points: 1,060,
Visits: 4,176
|
|
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 
If anbyone does know of something similar in SQL 2000 I would also be interested!
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 12:15 AM
Points: 244,
Visits: 300
|
|
| thanks for letting me know, regarding upgrading the server unfortunatly it's not an option for me
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 3:29 AM
Points: 1,060,
Visits: 4,176
|
|
| Nor me at present, but it's something to look forward to!
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 1:37 PM
Points: 4,
Visits: 356
|
|
| I think this script detects index rebuilds, which you might not always want. how can those changes be omitted ?
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 11:54 AM
Points: 90,
Visits: 584
|
|
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.
|
|
|
|