Re: Database Statistics... Best way to maintain stats???

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

you might look at using cubes for rollups. if you need realtime adhoc stats
(with slice and dice), then you want to use a snowflake or star schema.

since you are only doing 100k rows a day (pretty small actually), a simple
star schema should doit (with so rollups). with this low of volume, i'd
update the rollup tables in real time (simple trigger). i'd expect no query
to take over a second or two (unless it was years of detail).

-- bruce (sqlwork.com)


"Lucas Tam" <REMOVEnntp@xxxxxxxxxx> wrote in message
news:Xns96BEAE215B4C4nntprogerscom@xxxxxxxxxxxx
> Hi all,
>
>
> I have an application which logs a considerable amount of data. Each day,
> we log about 50,000 to 100,000 rows of data.
>
> We like to report on this data... currently I'm using a stored procedure
> to
> calculate the statistics, however since this is an ad hoc, reports take a
> while to generate.
>
> So how do you guys handle large amounts of data? Is there a good way to
> precalculate a a set of statistics to handle ad hoc queries (i.e. By Hour,
> By Day, By Week, By Month). Our application also provides near realtime
> statistics... so precalculation has to be done on a continual basis. Does
> .NET have any statistics classes that might help out with this sort of
> thing? I don't think Performance counters will work since they don't log
> persistent data.
>
> Any ideas?
>
> Thanks!
>
> --
> Lucas Tam (REMOVEnntp@xxxxxxxxxx)
> Please delete "REMOVE" from the e-mail address when replying.
> http://members.ebay.com/aboutme/coolspot18/


.