I have a client application that utilizes ADOMD today. This client
application has some custom MDX functions I've created and stored in a COM
library. We are able to utilize those functions within MDX 2000 by utilizing
the "USE Library" statement to make those functions available.

For certain reasons...it's not advantagous for us to have our fucntion
libraries reside on the Analysis Services box. We want the function
libraries to reside on the client machine.

How is this accomplished in ADOMD.Net and Analsyis Services 2005? It seems
the use library syntax is missing? Is there a substitute or are we hosed?

AS 2005 does all its execution on the server. Therefore you must register
the COM library as a server-side assembly. Unfortunately you cannot use a
client-side library.

I for one would like to understand why you *need* this functionality
though...

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

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

The issue is one of distribution. When you are delivering a cube browsing
application, it's generally not perceived as OK to interject you .DLLs onto a
previously established and working server at a client site. Requiring
modifications to existing and established database backends is not acceptable
practice.

Having the .DLL interace on the client side requires no such server database
side modifications and thus is perceived (and correctly so) by the user
community as non-invasive and safe.

This means the application distribution need not have any server side
installer and all relevant parts can be handled by client side installation.

I'm sorry to hear this functionality was lost. Any chance of it
re-appearing in service release...or a hot fix?

"Akshai Mirchandani [MS]" wrote:

Unfortunately not. As I said, AS 2005 does all MDX execution on the server, so usage of a library would require the DLL to be available on the server. In fact, most customers have complained in the past that they *don't* want to distribute these libraries to hundreds of client machines and then maintain them. That's why I was a little surprised at your posting...

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

-----Original Message-----
From: OLAPMonkey (AT) discussions (DOT) microsoft.com
Posted At: Tuesday, November 08, 2005 7:31 AM
Posted To: microsoft.public.sqlserver.olap
Conversation: What Happened To Use Library?
Subject: Re: What Happened To Use Library?



The issue is one of distribution. When you are delivering a cube browsing application, it's generally not perceived as OK to interject you .DLLs onto a previously established and working server at a client site. Requiring modifications to existing and established database backends is not acceptable practice.

Having the .DLL interace on the client side requires no such server database side modifications and thus is perceived (and correctly so) by the user community as non-invasive and safe.

This means the application distribution need not have any server side installer and all relevant parts can be handled by client side installation.

I'm sorry to hear this functionality was lost. Any chance of it re-appearing in service release...or a hot fix?

"Akshai Mirchandani [MS]" wrote: