Re: Single Cube from Multiple sources

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I think your errors are coming from not being able to query one server
from the other (as a linked server).
You can work around this.

1. Don't draw relationships in the DSV between tables that can't be
queried in the same query.
2. Manually add the dimensions to the fact table in the cube using a
"referenced" relationship.

The designer in VS lets you add tables from multiple data sources, and
it lets you draw relationships between them. But when you try to
process the resulting cube, SSAS generates a query that accesses all
related tables, and it must do so from only one server. If you look
at the SQL, you'll see that SSAS is creating a subquery of just the
key of the related table, and joining the subquery to the main table
on the foreign key. I think it calls this "materializing the
relationship." This behavior is actually triggered by a normal
dimension to fact table relationship that you set up in the cube
designer and that is generated by the existence of the lines in the
DSV.

One limitation is that you can't chain together referenced dimensions,
but you get the separation that you're looking for.

On Aug 17, 1:37 am, Satyajit Rout <satyajitr...@xxxxxxxxx> wrote:
Hi,

Could anybody help me on this urgently ?
Can we build a single msas 2005 cube from multiple datasources ? E.g.
I would like to keep all my dimensions in SQL Server 2005 DB and Fact
table in Oracle source. I am unable to achieve this. I receive
following errors in different oracle provider
....

.



Relevant Pages

  • Re: Performance Benchmarks?
    ... Are attribute relationships defined properly on the dimensions? ... If you run Profiler against the server, how long is spent in "Query ... I have created aggregations (Partitions tab in cube design). ...
    (microsoft.public.sqlserver.olap)
  • High CPU in client (Excel, OWC, Proclarity, etc.) accessing Analysis Services
    ... the OWC10 with 3 dimensions on the row axis, ... The largest size of any of these 4 dimensions < 360 members. ... Performance Guide to optimize the query, the cube, the server, etc. ...
    (microsoft.public.sqlserver.olap)
  • Re: Performance - Best Practices
    ... SP1 is applied on the server. ... I have also heard that parent child dimensions have a significant impact on ... I mean floating calculation and integer ... and the cube in front of this fact provide standard SUMS and DCount!) ...
    (microsoft.public.sqlserver.olap)
  • Re: Performance Benchmarks?
    ... adding memory on the server can help you; more data can be cached on the ... Here is my test query. ... )} DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM ... I have created aggregations (Partitions tab in cube design). ...
    (microsoft.public.sqlserver.olap)
  • RE: Troubleshooting Execution Location
    ... It's much faster on the server. ... If I run the query once via HTTP, then I change the date range and run the query again, it's almost instantaneous the second time. ... have you made sure that each Distinct Count measure is in a cube ... the axis that I think would benefit the most from aggregation doesn't show up. ...
    (microsoft.public.sqlserver.olap)