Trying to find out what records are accessed and what are garbage.

microsoft.public.sqlserver.programming

13 Jul 2006 12:43 PM

I have a program that reads a parameter table. The table has gotten quite
big and I don't know what values are actually used and what aren't. I have a
stored proc that you can call to get a value from the table but not
everybody/everything uses it (some stored procs reference the table.)

Is there any relatively easy way to know what records have been accessed and
what haven't? It would have to be at the table level because not everybody
uses the stored proc.

TIA - Jeff.

13 Jul 2006 12:59 PM

Jack Vamvas

unless you have been keeping a log table or can analyse the past log files
...no.

----
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________

Show quote

"UJ" <f***@nowhere.com> wrote in message
news:#4DCPonpGHA.4424@TK2MSFTNGP05.phx.gbl...
> I have a program that reads a parameter table. The table has gotten quite
> big and I don't know what values are actually used and what aren't. I have
a
> stored proc that you can call to get a value from the table but not
> everybody/everything uses it (some stored procs reference the table.)
>
> Is there any relatively easy way to know what records have been accessed
and
> what haven't? It would have to be at the table level because not everybody
> uses the stored proc.
>
> TIA - Jeff.
>
>

13 Jul 2006 1:21 PM

How about a SELECT TRIGGER?

Dejan Sarka posted an example here:
http://solidqualitylearning.com/blogs/dejan/archive/2004/11/25/214.aspx

This could affect the performance of the server, of course only for the time
needed for you to analyse the traces.

ML

---
http://milambda.blogspot.com/