I have a situation where I am using a named set with the following
definition:

SET [Top 25 Companies] AS 'TopCount([Client].[Company Name].Members,
25, [Measures].[Sales])'

I'm just retreiving the top 25 client companies by name. When I use
WITH to define the set, I get the set of 25 companies which have the
highest sales in the tuple that I am selecting. So far so good.

When I create the named set in Analysis Manager, the set always
retrieves the top 25 companies for the entire cube, not the tuple in
my particular query.

Example:
WITH
SET [Top 25 Companies] AS 'TopCount([Client].[Company Name].Members,
25, [Measures].[Sales])'
SELECT
{ [Measures].[Sales] } ON 0,
{ [Top 25 Companies] } ON 1
WHERE [Sale Date].[2001]

This will return the companies who have the highest sales in 2001

Now let's say [Top 25 Companies] is created in Analysis Manager:
SELECT
{ [Measures].[Sales] } ON 0,
{ [Top 25 Companies] } ON 1
WHERE [Sale Date].[2001]

This will return the companies who have the highest sales across all
years, and then show the sales for those companies in 2001 (some of
which come back with 0). This is not what I want.

I need to be able to create the named set for use in a 3rd party
package, but I want it to work like the query-scoped (i.e., WITH
SET...) set. Is this possible? What am I missing?

Thanks,
Rick

Named sets can either be created as a DSO Command object, in which case they
are automatically executed when the session starts (as Jamie pointed out)
and are not dependent on any query itself -- they will run regardless of the
query -- or a front-end tool can execute them in session scope, which is
what Rick is asking for. Unfortunately to do the later requires support from
the front-end tool itself, i.e. that it queries some metadata somewhere and
execute each named set in session scope. This isn't something that the
server will do for them automatically. Sorry.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jamie" <Jamie (AT) discussions (DOT) microsoft.com> wrote

query-sensitive.