It is right that i can't use user defined scalar database functions in
expressions for member key column, name column?
--
Juergen

Member key columns are based on the capabilities that exist in the
underlying relational engine behind the data source associated with
your cube. They have nothing to do with specific capabilities of
Analysis Services. So for instance, if you are using SQL Server as
your data source for building your cubes, you can certainly utilize
user defined functions created in the SQL Server relational database
engine in conjunction with the creation of a member key or member name
in Analysis Services.

Be careful here. In SQL2K, you can type anything you want into a column and
it is just carried through to the source RDBMS. Thus you can do some
interesting operators, such as combining two fields together like

LAST_NAME + ', ' + FIRST_NAME

This is acceptable to SQL2K, because we just carry it along. Obviously since
this is TSQL syntax, it wouldn't work with Oracle, but it has similar
operators.

In SQL2K5, key and member name columns have to be real columns. If you want
to do operators like this, then you need to encode them in derived columns
in the DSV. Thus while you can do it, it looks quite different in SQL2K5 --
you must be specific.
--
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.


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