I am hoping somebody has more experience with Personalization Extensions than I and can provide ideas for how I might conditionally run different command operations in the "CubeOpened" event.
After investigating Microsoft.AnalysisServices.AdomdServer.Context, it appears that I have some minimal information that I can use to conditionally run different commands during personalization.
For example I can identify the current server, cube, and user. But I'd like to be able to go further than this. My personalization extensions can be a bit slow (a few seconds). Because the exact same cube could be used in different scenarios, (via Excel, custom applications, reports, etc), it is not always a requirement to perform the personalization work. I don't always want to pay the penalty of waiting for personalization extensions to initialize in every scenario.
Ideally I would have access to the full connection string and I would be able to disable personalization extensions for certain connections based on the current application name (as it can be viewed in SQL profiler).
Has anyone tried to execute personalization code on a conditional basis?
David Beavon