I'm experimenting with programmatic ways of updating cube data. I came
across an example in SQL Books Online. I clone a temporary partition, point
it to the desired fact table that has additional data, and then attempt to
process it. But when I call the Process method I get an Interop error
telling me that I have an "Invalid fact table alias". If I just process the
partition via Analysis Manager then it's fine. Does anyone know what's
going on here.

My advice is to get the Metadata Scripter that is contained on the SQL
Server 2000 Resource Kit (available on a TechNet Resource Kit CD/DVD, or at
your local bookstore :-)

It will take a AS object and reverse engineer it into a VB program to
re-create it. So your steps would be:
1) Run AM and create the partition
2) Run the metadata scripter and generate a matching VB program. Let's call
it "Program A".
3) Run AM and delete the partition.
4) Run your application and create the partition
5) Run the metadata scripter and generate a matching VB program. Let's call
it "Program B"

If you compare Program A with Program B (use a tool like windiff for this),
I am sure that you will find that there is some property that you have not
setup properly.

Hope that helps.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Ves Sladin" <VesSladin (AT) friedrichklatt (DOT) com> wrote

Thank you for the reply, but based on what you wrote I think I need to make
an additional clarification. Namely, in my debugging, the only thing I've
done in Analysis Services is to attempt to Process. In other words, it's
not like I'm comparing going through these steps in Analysis Services vs
going through them programmatically. In both cases, all steps except for
processing are done through code. It's just that issuing a process command
in Visual Studio didn't work. So, I went to Analysis Services to see if the
partition was visible, and since it was, I thought I'd try to process it
there. That worked. Therefore, Analysis Services sees the partition as
properly constructed and is able to work with it, which implies to me that
there shouldn't be anything wrong with the definition of the partition.

So, if my logic is right, doing what you suggest would imply that simply by
opening Analysis Services and looking at the partition there, I've somehow
changed it's definition. Is this what you're implying? Please clarify.
Thanks Again.

Ves

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote