We have a number of clients accessing our OLAP database, and each of
them has a potentially unique subset of attributes on each dimension
they can access. We originally tried implementing this using
perspectives, but it seems that when we load up the OLAP server with
several hundred perspectives, trying to browse the cube causes the CPU
to spike up to 100% for 5-10 minutes. It eventually snaps out of it, but
subsequent connections cause the same behavior. Obviously this is bad --
are there any suggestions about how to filter out these attributes
and/or get the perspectives to behave?

what about security?
have you try?

"Greg Fodor" <nebby101 (AT) hotmail (DOT) com> wrote

Unfortunately OLAP security seems to provide no way to eliminate the
visibility of an entire attribute, merely attribute members.

Jéjé wrote:

How many perspectives do you have? This CPU spike, what happens when you do
this remotely, is the CPU spike on the client or on the server. Please look
at memory used on both the client and the server -- what is it like?
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Greg Fodor" <nebby101 (AT) hotmail (DOT) com> wrote

Hey Dave,

We were trying to build a number of perspectives for each of our
clients, so it was pushing 500 or so. The spike is on the msmdsrv.exe
process. We've since worked around it somewhat by using display folders
combined with translations to filter out attributes/measures for each
client by assigning them a locale to connect with. Ugly, yes, but its
the only way to do it it seems right now.

-Greg