I am using the ADOMD.NET library in a C# aspx page to access Analysis Services in the June CTP of SQL 2005.

What I'd like to do is retrieve the full paths of the Members I receive in a CellSet. I understand there will be a way in the released product to configure the server to return full paths in the UniqueName property of members, but that this facility is not available in the current builds.

In the absence of the configuration setting, I do a recursive call for each Member in the CellSet to walk through its ascendants and form the full path by concatenating Caption strings.

I recall the advice from SQL 2000 being that accessing metadata is much faster than running queries, but that is not what I find with SQL 2005. In fact, the process I've described is spectacularly slow.

As an example, a query which resulted in 286 .Parent accesses took 20 seconds to process. Executing the query itself and returning each Member's UniqueName property takes a much more reasonable fraction of a second. (I.e., the 286 .Parent and .Caption calls appear to account for almost all of the 20 seconds of processing time.)

Can I expect this to improve in the released product? Is there an alternative to the two I've mentioned for retrieving full path information for Members?

Thanks for the help.