hello,

how does compression work in tabular? I don't pretend a full explanation, my doubt is

i've processed a 4 partitions of a factual and i saw in its properties 517 MB, i processed all the other factuals and dimensions and i saw again 517 MB. Then i've done a change in a view for a dimension, processed just this dimension and this morning i see 1300 MB ??????

regards

We are using SQL Server 2016 and Tabular model 1200. I have created a model with perspectives on it and built a live connected power bi report on one of the perspectives. When I click refresh then some of the random visuals breaks and if see details it's showing me the following error. I never faced this kind of error prior implementing the perspectives in the model. Can any one help me with this ? It's a production issue. If I hit refresh for Couple of times then it's working.





Hi,

I have an existing cube that I need to separately add a few attributes to a perspective and this all needs to be done dynamically, not in design mode, but as part of a ongoing ETL job

In the past I have received XMLA files and executed them via SSIS component, so this part I am familiar with.

My question is  - How do I build this described above specific XMLA that deals only with the adding a few attributes to a perspective ?

Do I need to take it from the full XMLA of the whole cube and rebuild it, or can I somehow get the XMLA script from SSMS by drilling to the  relevant part, creating a smaller XMLA ?

Thanks,

Dani

Hi,

I have an existing cube that I need to separately add a few attributes to a perspective and this all needs to be done dynamically, not in design mode, but as part of a ongoing ETL job

In the past I have received XMLA files and executed them via SSIS component, so this part I am familiar with.

My question is  - How do I build this described above specific XMLA that deals only with the adding a few attributes to a perspective ?

Do I need to take it from the full XMLA of the whole cube and rebuild it, or can I somehow get the XMLA script from SSMS by drilling to the  relevant part, creating a smaller XMLA ?

Thanks,

Dani

I created the SSAS Tabular Data Model Solution in VS 2015 and Deployed that in SSAS 2016 Analysis services. After deployment I could not see any Object under any folder. can you please help me with this.

DAX: How to get a MAX value from a calculated measure  ?

Total CC :=   SUM( col1 )  

 MAX( [Total CC]) 

Thanks!

Hi,

We have made changes to some of the fields in our DimCustomer table and SSAS is now complaining with the errors below.

Address_Line fields were increased from 30 to 50 characters and we fixed those. But, we can't figure out what is wrong.

How do you work out which other column(s) is causing problems?

<return xmlns="urn:schemas-microsoft-com:xml-analysis"><results xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Warning WarningCode="2165374978" Description="Errors in the back-end database access module. The size specified for a binding was too small, resulting in one or more column values being truncated." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Address Line2' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3239837702" Description="Server: The current operation was cancelled because another operation in the transaction failed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'AML Risk Category' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238002695" Description="Internal error: The operation terminated unsuccessfully." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'AML ID Filter' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Activity' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Authorisation' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Customer Name' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Nationality' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'AML Vml Score' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Standard Industry Code Description' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Date Of Birth' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Joint Nationality' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Post Code' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Country' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Address Line3' attribute of the 'Customer' dimension from the 'SPBUK_DW-BI_Cubes' database was being processed." Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" /></Messages></root></results></return>

Hello, 

Could anyone please post an example of how to create a SQL CLR stored procedure that would work with SSAS Tabular. 

We are currently querying our SSAS DB with stored procedures by using MSOLAP (Microsoft OLE DB Provider for Analysis Services 14.0)  Provider and a linked SSAS server. This approach works fine. However, we noticed that some newer DAX functions are not being recognized by MSOLAP,so the next step is to try SQL CLR where we can use AMO    Microsoft.AnalysisServices.AdomdClient. We need a working pattern of SQL CLR  + SSAS Tabular . 

Any ideas or suggestions will be highly appreciated. 

Thanks, N 

Hi guys,

I have and MDX issue and I hope you can help me. Actually in my data I have 1 Date Column.

However I am using it for 2 different Dimensions (Reporting Period and Comparison Period).

Now I have Measures (f.ex. Revenue) that are connected to only 1 Date Dimension.

I implemented it by using MDX, f.ex. based on the Revenue Measure:

Revenue Measure based on Reporting Period:

CREATE MEMBER CURRENTCUBE.[Measures].[RP_Revenue]
 AS 
([T-DIM ServiceDateReporting].[ServiceDateReporting].[All],[Measures].[Revenues]) 
,
DISPLAY_FOLDER = 'ReportingPeriod';

and the same Revenue Measure based on the Comparison Period:

CREATE MEMBER CURRENTCUBE.[Measures].[CP_Revenue]
 AS 
([T-DIM ServiceDateComparison].[ServiceDateComparison].[All],[Measures].[Revenues]) 
,
DISPLAY_FOLDER = 'ComparisonPeriod';

Actually the implementation works really well.

In Excel I can use both Measure and both Date Hierarchies as Filter and they are only connected to one Date Filter. So if I filter the Reporting Period to Dez. 2018 RP_Revenue does show the data from Dez. Additionally I can filter the Comparison Period to May 2018 and the CP_Revenue does show the data for May 2018.

So far so good, however I am not able to use YTD cumulation anymore.

I am creating a Cumulation Member:

CREATE MEMBER CURRENTCUBE.[Cumulation].[Cumulation].[YTD]
 AS NULL
,VISIBLE = 1;

Now I am scoping the YTD Member:

SCOPE([Cumulation].[Cumulation].[YTD]);
	SCOPE([T-DIM ServiceDateReporting].[T-DIM ServiceDateReporting].MEMBERS);
		THIS=Aggregate({[Cumulation].[Cumulation].[Cum].&[1]}*
		{PeriodsToDate(
[T-DIM ServiceDateReporting].[T-DIM ServiceDateReporting].[Year], 
		[T-DIM ServiceDateReporting].[T-DIM ServiceDateReporting].CurrentMember
)});
	END SCOPE;

	SCOPE([T-DIM ServiceDateComparison].[ServiceDateComparison].Members);
		THIS=Aggregate({[Cumulation].[Cumulation].[Cum].&[1]}*
{PeriodsToDate(
		[T-DIM ServiceDateComparison].[ServiceDateComparison].[Year], 
		[T-DIM ServiceDateComparison].[ServiceDateComparison].CurrentMember
)});
	END SCOPE;
END SCOPE;

Actually YTD is working for the first SCOPE, ServiceDateReporting but the second SCOPE statement is not working (ServiceDateComparison).

How can I implement the YTD cumulation that the measures using the reporting period are cumulated based on the reporting date Hierarchie dimension and measures using the comparison period are cumulated based on the comparison date Hierarchie dimension?

Thanks a lot!!

Elchfighter

--Below is the query for the EnteredDate parameter dataset in my SSRS report. 
--The problem is that too many dates are displayed in the dropdown since it is a datetime field.
--I want this dataset to be filtered by a date that is passed like the query further below but I can't seem to get that to work
--because this query deals with MEMBERS and in the query further below I am creating a SET.
--Also, the dimension only has [Entered Year], [Entered Quarter], [Entered Month] and [Entered Date] which is a datetime field.
--I don't have just a day field and that is the reason I am doing an Instr comparison to filter the SET.

WITH MEMBER [Measures].[ParameterCaption] AS 
[Dim Cash Transaction].[Entered Date].CURRENTMEMBER.MEMBER_CAPTION 
MEMBER [Measures].[ParameterValue] AS [Dim Cash Transaction].[Entered Date].CURRENTMEMBER.UNIQUENAME 
MEMBER [Measures].[ParameterLevel] AS [Dim Cash Transaction].[Entered Date].CURRENTMEMBER.LEVEL.ORDINAL 
SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , 
[Dim Cash Transaction].[Entered Date].ALLMEMBERS ON ROWS 
FROM [Cube]
WHERE ( [Dim Cash Transaction].[Entered Year].&[2016],[Dim Cash Transaction].[Entered Month].&[3] )

--I want to narrow down the EnterDates that are displayed in the dropdown by
--passing in a date that the user will provide kind of like this unless there is a better way.

WITH SET [EnteredDates] as
{FILTER([Dim Cash Transaction].[Entered].[Entered Date].MEMBERS,
(Instr(1, [Dim Cash Transaction].[Entered].CurrentMember.NAME, "2016-04-08") <> 0)  )}
SELECT {[Measures].[Disbursement Count],[Measures].[Net Contract Retail Amount]} ON columns, [Entered Date].ALLMEMBERS ON rows
FROM [Cube]

I am no expert but I know there is a lot wrong with this dimension; however, it is what I have to work with for my report.

I have a cube with many facts and dimensions.

But for this issue I will just point out the one fact and dimensions I'm having issues with

I have fact call it Financials and two dimensions Account and say Income Statement. 

the financials have an account_id that reference both Account dim and Income Statement dim.

Not all account_id from the fact (fact_financials) are in the Income Statement dim (dim_IS) but should be in the Accounts dim (dim_account).

So in order to process the cube have set ErrorConfiguration to Custom on the fact measure group. Along with KeyNotFound = IgnoreError.

But this for all the keys link to that measure group. I would like to make sure that all the account_id in the fact are in the dim_accounts since they should be, how can I do that? 

I need to reduce partition processing time with ProcessAdd (incremental processing) and few new rows in SSAS 2014.

Currently, processing a partition of SSAS cube with ProcessAdd and few new rows (<10) takes 920 ms. According to SQL Profiler, in the processing, loading new data takes about 20 ms, aggregating 300 ms, updating/saving measurement groups and cube takes 600 ms. I know if I enable "Lazy aggregation", aggregation can be delegated to background threads and thus incremental processing time can be reduced. In that case, how can I incrementally process a partition without aggregation? I know ProcessData option would only load data after deleting existing data in the cube (i.e., no incremental process).

Any clue will be appreciated.

Hi

I need help with the following error soon please

"Error 16 Errors in the metadata manager. The 'Dim_Item' many-to-many dimension in the 'Fact Analytics Data' measure group requires that the granularity of the 'UTC Local Time Together' dimension is lower than that of the 'Bridge Aggregate Info Analytics' measure group.  0 0 "

This is how my data source view looks  and dimension usage tab looks like.

Hi!

Very briefly, my goal is to incrementally process the fact data for my SSAS 2005 cube, without losing aggregations.

For that purpose, I have defined all attribute relationships as rigid (I don't really expect any of the relations to change) because I hear that flexible aggregations get dumped during incremental processing. BIDS Helper indeed confirms that all of my aggregations are rigid.

Then I proces the cube, either via the SSMS GUI using the "Process Incremental" option, or with an XMLA command using type "ProcessAdd". The outcome is the same, no matter which method I use.

Then I check the status of my aggregations. I do so first by sending a DISCOVER_PARTITION_STAT Discover XMLA query (http://geekswithblogs.net/darrengosbell/archive/2008/12/02/ssas-are-my-aggregations-processed.aspx), and, as a double check, by sending a query to the cube from which I know it normally uses an aggregation and checking in the profiler whether the aggregation is really used.

The result is always the same: The aggregations are lost! The DISCOVER_PARTITION_STAT query informs me that all aggregations have size = 0. Note, that after a ProcessFull, all aggregations are there (with size > 0) and work as expected, so the problem only occurs after incremental processing. Also for the problem to occur it is enough to incrementally process the cube, the dimensions are left untouched.

I have performed some experiments on simple cubes based on the Adventure Works DW database, where everything works as expected, and aggregations are not lost, also after incremental processing. So in principle I can achieve what I want, just not yet with my actual project. I do not know how my project is different from that small test I set up, except for size and complexity of course.

Does that sound familiar to anyone? How could I go on to diagnose what's going wrong? What can I possibly have messed up?

Thanks and regards,

Peter.

Hi Guys,

I have 2 cubes(Cube_A & Cube_B) and 2 DSVs (DSV_A and DSV_B). Dimensions are based on both DSVs. Now I got a requirement to move one cube Cube_B to another server and in that case I want to change DSV of those Dimensions pointing to DSV_A to DSV_B so that I can get rid of DSV_A completely. 

After doing this, I will have only one DSV_B and Cube_B and all the dimension in the Database will be coming from DSV_B.

I Got below option, I have not yet tried. But there is any other way to change this from UI?

http://dineshpathirana.blogspot.com/2011/11/how-to-change-datasourceview-of.html

How to change the DataSourceView of an existing dimension

If you have two or more data source views on your analysis service project, there is a definite possibility to create dimensions using wrong data source view. But you may have confused later on, since SSAS doesn't provide you a direct way to re-change the data source view.

I found that error recently, when I deleted some columns from the Time Dimension on the database, but it wasn't reflect on my Time Dimension on the cube. When I right click and click on 'Edit Data Source View' on the Data Source View pane of the dimension editor window, it was redirected me to a different data source view. So it was a good way to identify whether the dimension is being created using appropriate data source view.

But the solution was rather simple. You only have to do open the dimension using code view and change the DataSourceViewID tag to correct data source view. (It is recommended to get the correct data source view ID from another dimension if possible)

Above method can be used to change the data source view from an existing cube as well.

Finally I would like invite you to read my new and more interesting article on How to use Forex Trading as Part Time Earning Method. It would be more beneficial and interesting thing for you.

Thanks Shiven:) If Answer is Helpful, Please Vote

In my fact table, I have rows with measures columns with NULL value (in the Database).

When I browse my cube, I get a 0 for all my measures with a NULL Value.

Thank you for your help.

Hi 

   our dim_vip table have 40000000 rows of data every day we process it on ssas is very slow about 40 Minute、

we want konw  there are any ways to process it quickly ？can we only process Changing data？

    thank you

very much

Hi,

I ran into the following error when trying right click Fact Product Forecast partition to bring up theEnable Writeback dialog box (screenshot included). I am using VS 2012 and SQL Server 2012. This is from the code files included with the textbook "Microsoft SQL Server 2008 Analysis Services" by Scott Cameron. I was able to successfully enable Dimension Writeback but the Cube Writeback failed.

I have SP3 installed on SQL Server 2012.

Microsoft SQL Server 2012 (SP3-GDR) (KB4019092) - 11.0.6251.0 (X64)
    Jul  7 2017 07:14:24
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 17134: )

The specific error message is "Could not load file or assembly 'SqlWorkbench.Interfaces, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (Microsoft Visual Studio)."

Any help much appreciated.

Hi,

when i have access for all members mdx working fine. while applying Dimension security i am getting the following error.

members tuples or sets must use the same hierarchies in the function.

Thanks,

Narendra

Hi guys,

We are looking into switching from our current multi dimensional cube to a Tabular model.

One of my dimensions (called PL) look like this:

PL_KeyPL_Category
0        Unknown
1        Product Revenue
2        Service Revenue
3        Intercompany Sales

What I need is to add a calculated row called "Total Revenue", which is Product Revenue+Service Revenue+Inter-company Sales. In the multi dimensional cube is easy, and it looks like this:

[Dim PL].[PL Category].&[Product Revenue]+

[Dim PL].[PL Category].&[Service Revenue]+

[Dim PL].[PL Category].&[Intercompany Sales]

My question is, how do I go about that in DAX? is it at all possible?

Thanks in advance, Zeev.