Combine data from multiple SSAS cubes in PowerBI - ssas

I need to combine data from multiple SSAS cubes and visualize in one dashboard. It seems only one SSAS cube can be added to Power BI desktop, there is an option to import data as a flat table but in this case cube structure would be falt and useless.

you are right, only one cube can be accessed at design time using the live connection.
2 ways to solve your problem:
1 - build a new cube, accessing all the data that you need
2 - switch to import mode and build your own model
good luck!

Related

DAX Development: How to process a small portion of your data without importing millions of records in your machine? (SSAS Tabular Model)

We are currently using Visual Studio 2015 to develop SSAS tabular models. Our tables consist of more than 100M records of data. Is there a technique or practice where in I won't need to import all of the 100M records to Visual Studio and just use a small portion of the data during development?
Right now, I just limited the data by selecting top 100,000 records in the VIEW that we are using and imported it to Visual Studio so that I won't processed 100M records in my machine. Once the project is deployed, we remove the SELECT TOP 100,000 from the VIEWS and reprocess them so that it would pick up the full dataset of 100M records.
Is there a better way to do this? Like using sample partition used for direct query cubes but for in memory cubes?
Is it suitable to use row level security to restrict the data sets when selecting from the view so my account returns a subset compared the agent service account?
I would say that the best practise is what you are already doing (and what I'm currently doing).
Start your cube with a small sample (between 1000 and 100000 rows for example). Once it's as you want it, deploy it. Then use SSMS to remove the sample and process your cube (with full data) and you will have a complete cube.
It's not really helpful because it's what your are doing now but it's the right way to do it.

How to mix SSAS with other sources in PowerBi

Using PowerBi we cannot find any way to mix data coming from SQL Server Analysis Services with other data sources (Excel to make it easy).
As soon as we select the SSAS data source, the new source button is greyed and no way to use it.
Trying the inverse (Excel first) seems to work but importing specific SSAS data (which in our case is several milion rows) so in fact is hardly usable as we have to know in advance what columns are we going to use for every report ... not quite user friendly!
Is there any way to do it the "logical" way?
thks
PowerBI does not allow to mix DirectQuery with other data sources.
If it fits your task you could use your source in Import mode instead.
https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-use-directquery/

Possible to Create OLAP Cube filtered by dimension?

I hope this is a quick yes or no question and I believe the answer is yes, but wanted to confirm with someone more knowledgeable than I.
First the background story: We've just started using OLAP cubes where I work and have one setup each for financial, staffing, and project data (3 cubes) in our new ERP system. We have several offices where this data is needed, but we don't want for them to have access to the other office's data. There are only a few individuals in the organization that have access rights to these 3 online cubes.
For distributing the appropriate set of data for the individual offices, the solution I've currently come up with is to create offline cubes that are connected to pre-configured excel files (using Excel 2013 Standard or Plus). Each offline cube is created via the "CREATE GLOBAL CUBE" MDX command and then is filtered via one of the dimensions (see below).
This solution has not been very effective as these offline cubes use absolute paths in the excel connection files. We've been remotely connecting to the users desktops to reconnect the offline cube that gets distributed to them. This process is not very effective as it seems excel sometimes doesn't want to reconnect to the offline cube and in some instances simply won't work.
The question: Is there a way to create an online cube that has been pre-filtered on a particular dimension so that I can allow access to their online cube for only their data rather than using offline cubes?
I've listed the commands I'm using to create the offline cube below as an example of what I'm looking for.
Cheers
CREATE GLOBAL CUBE
[Offline Cube Name]
STORAGE
'C:\SomeFile.cub'
FROM [Online Cube Name] (
MEASURE [Online Cube Name].[Some Measure 1],
MEASURE [Online Cube Name].[Some Measure 2],
DIMENSION [Online Cube Name].[Dimension].[Office Name]
(
LEVEL [Organization],
MEMBER [Organization].&[Office Name]
)
);
If you have been completely successful with local cubes count yourself lucky as they are tricky. But I would recommend you avoid them.
Instead setup role-based security in the cube and let users connect live. If you have a list of Active Directory users or groups per office and want to create one role in SSAS per office follow this approach. If you prefer to add a few hidden tables to the cube that drive security then use the dynamic security approach.

my cube browser doesnt show the measures?

I have performed ETL operation and i created a data warehouse and i loaded the data to it and so far its fine.. my ETL seems to work allright since my data warehouse contains all the data i needed. And then i created an SSAS project from my data warehouse following the AdventureWorks DW example. I deployed the cube and processed it. Then i tried to browse the cube. But here is a problem, it seems as the members do exist but the measures are empty. because my dimensions contain the data but when i throw the measures to it .. it is just gonna be empty cells. What causes this?
In the cube designer, check the "Dimension Usage" tab. Make sure that the intersection between a dimension and a measure group has something there (If there's meant to be a relation).
What happens if you drag & drop the measure to the browser, without any dimensions?
Also what version of SSAS are you on, is it 2005? That had IgnoreUnrelatedDimensions set differently to 2008 I think..
Make sure you've linked your dimensions with measure groups (i.e. that you fact table references you dimension tables).
Also make sure you have foreign keys defined in your data warehouse (as soon as wizards in Visual Studio use them when proposing cube structure).
In order to deploy to a different dwh server
Right Click on the CubeNAME
Go to properties
In Configuration properties > Go to Deployment
In Processing option - change Default to - Do not Process.
if in case the DB is very large and keep huge data, it will get deployed and you can process it later.
For Target - Set name of Server
Click on OK, Deploy and later process

ROLAP not working - how to design the cube/DSV for ROLAP?

I'm trying to configure storage mode ROLAP for a partition in an existing SSAS cube. The cube is a little messy in that the measure group is defined by a named query (as opposed to a table) and the dimensions are defined in several different data source views (DSV).
This is the error message I get when querying the cube with mdx:
Executing the query ...
Server: The operation has been cancelled.
Errors in the high-level relational engine. The 'dbo_dim_account' table that is required for a join cannot be reached based on the relationships in the data source view.
Execution complete
Note that MOLAP storage mode with proactive caching works fine. This problem occurs only when storage mode is ROLAP or HOLAP.
Also, I have tried to add the tables of all dimensions to the DSV of the cube in question but that doesn't seem to help.
Any ideas?
Not an expert here, but you could try importing the AS DB in Visual Studio.NET - "Import Analysis Services database" in the New Project... dialog.
Once in there, you can see the table schemas for the Data Source View (which is where the relational tables are defined that the cubes are extracted from). Next, look to make sure the "dbo_dim_account" table is there and that your fact table is related to it.
It may be that a dimension and fact have to be in the same DSV for the relation to work?
Also, maybe the SSAS flight recorder or Application log would have more issues?