November 15, 2002 at 8:44 am
Is there a method (3rd party application, stored procs, triggers (could get nasty as the table count grows), (your idea here), …) to track the number of selects/updates/deletes on all tables within a database? I thought a trigger on each tables for each update/delete which would increment a counter related to that table in a statistics table would do the trick but that doesn’t cover a select on said table. I'm attempting to identify the tables in a database that are no longer being used by any part of the application which relies on it hence no selects/updates/deletes on it. Any ideas???? Thanks
November 15, 2002 at 9:18 am
As you have mentioned one canot keep track of the selects using the triggers,I think you can get this information by running the trace several times with intervals(for performance) and saving it to a table or a file.Analyse the information which is saved.
November 15, 2002 at 4:51 pm
If you need to capture adhoc sql i.e. not sps then profiler is your only option. I am not sure if luminent log explorer captures that info
Simon Sabin
Co-author of SQL Server 2000 XML Distilled
http://www.amazon.co.uk/exec/obidos/ASIN/1904347088
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
November 15, 2002 at 4:56 pm
Profiler is your only shot
Steve Jones
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply