|
Home > Archive > MS SQL Server OLAP > November 2005 > Slicer performance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Slicer performance
|
|
| Jimmy 2005-11-28, 11:24 am |
| Hi,
Does placing a tuple in the WHERE clause differ, performance-wise, than
crossjoining the set with that tuple?
Thanks.
| |
| Denny Lee 2005-11-28, 1:23 pm |
| It should not - but its best to experiment to see. In general, there should
be little difference because since you're typically specifying a specific
member within the where clause. Then applying this same member to a
crossjoin should have little effect expect for the additional axis that you
would need to view in the output that you wouldn't normally have with the
where clause. An example of where it would be faster in the crossjoin is
that if you were going to place into the where clause a set of values (vs. a
single member). If you were to use a NonEmptyCrossJoin, this probably is
faster than using a regular crossjoin or placing it in the where clause.
But in general, there should be little difference between the two.
--
HTH!
Denny Lee
< dennyglee_at_hotmail
_dot_com>
Blog at:: http://spaces.msn.com/members/denster/
"Jimmy" <NoSpam> wrote in message
news:uWLo%23SD9FHA.3132@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> Does placing a tuple in the WHERE clause differ, performance-wise, than
> crossjoining the set with that tuple?
>
> Thanks.
>
|
|
|
|
|