RE: creating degenerate dimension (with invoice numbers)
- From: "SQL McOLAP" <SQLMcOLAP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Aug 2005 06:39:16 -0700
One might argue that invoice detail like this isn't best suited for OLAP.
When clients say they want things like order numbers or invoice numbers in a
cube, I try my best to discourage it, since invoice and order numbers are
usually detail attributes that don't really aid in analysis. If you have an
invoice number dimension (a dimension with invoice number as the lowest
level), or you have a member property for it, I'm afraid you'll be paying a
performance price either way. The more appropriate way to handle this would
be via SQL reporting, if it's an option.
"Bartosz Gorzynski" wrote:
> How can i this - sometimes i need include invoice numbers in reports
> (fact table size 2475797, distinct invoice numbers 177014). Nonempty
> crossjoin - products,customers and invoices( invoice_status,invoice
> number with auto grouping parent) is very slow
>
.
- References:
- creating degenerate dimension (with invoice numbers)
- From: Bartosz Gorzynski
- creating degenerate dimension (with invoice numbers)
- Prev by Date: RE: Cube design
- Next by Date: Re: views
- Previous by thread: creating degenerate dimension (with invoice numbers)
- Next by thread: Re: creating degenerate dimension (with invoice numbers)
- Index(es):
Relevant Pages
|
