![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I'm getting a different result set back for a particular query which slices on an extremely simple calculated member (the calc. member is just defined as the All member for one of my dimensions). The query uses NON EMPTY on the rows returned, and when run without a NON_EMPTY_BEHAVIOR hint on the calc. member, it returns 10 rows. When run with a hint (NON_EMPTY_BEHAVIOR={} even works for this), it returns 20 rows. I've determined from the subject matter database that 20 rows is correct. Anyone else have any experience with this problem, or know why I might be experiencing it? Thanks, Will. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hi Will, Could you reproduce this behavior in a sample Adventure Works query? - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |