Re: Is Cube a Good Option for Me?
- From: Nestor <n3570r@xxxxxxxxx>
- Date: Wed, 29 Aug 2007 16:37:27 -0700
It might help but it really depends on how your report is intended to be. If its just a adhoc report that fetches the data from your database on demand and real time data is required, then it might be best to keep it as a huge store proc with optimized indexes and query statements.
If however you have the option to have it query historical data, maybe update to the latency of an hour, you can try to create a cube out of it but that will mean that more database maintenance on your end.
On Wed, 29 Aug 2007 08:39:53 -0700, Doomed ReportsGuy <doomedreportsguy@xxxxxxx> wrote:
I need to replace a single slow view with a faster object that makes
several joins on some 36 tables/views (for reporting). I would like to
create a cube on a seperate server that has this same functionality, but
at the hopes that it improves performance and allows my report writers
to connect to it easily. Believe me, I'd rather break it up into smaller
objects, but can't at this time.
The only other thing I could think of is a huge proc, but I don't think
I would gain much from it. Would a cube be good for this?
Suggestions appriciated.
DoomedReportsGuy
*** Sent via Developersdex http://www.developersdex.com ***
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
.
- References:
- Is Cube a Good Option for Me?
- From: Doomed ReportsGuy
- Is Cube a Good Option for Me?
- Prev by Date: Is Cube a Good Option for Me?
- Next by Date: Re: SSAS reports, Proclarity and MOSS 2007
- Previous by thread: Is Cube a Good Option for Me?
- Next by thread: Re: SSAS reports, Proclarity and MOSS 2007
- Index(es):
Relevant Pages
|
Loading