|
|
Posted by Tony Rogerson on 11/03/05 09:55
Hi Casperin,
Are you building cubes over this data to give dimensional reporting?
Have you taken a look at the SQL Server 2005 BI offering (Analysis
Services), there are a lot of very useful things in there to help you build
a tight scalable and performant solution.
There is a lot of pro-active caching in there, aggregates pre-populated
etc...
Starting point: http://www.microsoft.com/sql/analysis/overview.mspx
Tony.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CasperinMiami" <UseLinkToEmail@www.dbforumz.com> wrote in message
news:919514_9c1d7ce8d71da5298da69d80e17464c3@dbforumz.com...
>I have a problem in a datamart my team is developing. There is a
> split in approach within the team, one side taking the approach of
> having a huge Fact table (resulting in literally billions of rows of
> data) and another team having a fairly flat model that will result in
> less rows, but longer response time to execute the BI queries.
>
> My question is this: At what point does a FACT table too large? At
> what point is a model for Business Intelligence too unwieldy and that
> a compromise be agreed to for response time vs load and 'completeness.
>
> Thanks,
>
> -C
>
> --
> Posted using the http://www.dbforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
> http://www.dbforumz.com/help-big-data-mart-model-ftopict267633.html
> Visit Topic URL to contact author (reg. req'd). Report abuse:
> http://www.dbforumz.com/eform.php?p=919514
Navigation:
[Reply to this message]
|