Re: Rates of change???

From: Madison Pruet <mpruet_at_attbi.com>
Date: Sat, 28 Jun 2003 19:11:55 GMT
Message-ID: <%LlLa.44878$Ab2.72820_at_sccrnsc01>


Well...

  1. To determine the fuzziness of a copy of a table as it ages
  2. To determine how often an ETL process needs to be run
  3. To project the impact of replication of a table

etc...

I suspect that other folks can think of reasons why the rate of change of a table might be a significant piece of information as well.

"Anna C. Dent" <anacedent_at_hotmail.com> wrote in message news:13lLa.113302$MJ5.44531_at_fed1read03...
> Madison Pruet wrote:
> > Hi,
> >
> > Is there an easy way to determine the rate of change for table? I
 realize
> > that I could do periodic select count(*) from XXX, but that would only
> > determine the size of the table. It would ignore updates.
> >
> > What I'd really like to do would be able to determine the number of
 non-read
> > operations over a table so that I can determine the rate of change for
 that
> > table.
> >
> > Thanks for any help..
> >
> >
> >
> WHY?
>
> I can't think of any significant benefit
> which might result from having these "facts".
>
> Once you had these numbers,
> what good would they do you and
> what would you do with them?
>
> What problem are you really trying to solve?
>
> What exact metrics exist to prove a problem even exists?
>
> How will you (or anybody else) know conclusively
> that the problem has been solved?
>
>
>
Received on Sat Jun 28 2003 - 21:11:55 CEST

Original text of this message