Errors in the OLAP Storage Engine for a large dimension

Monday, March 3, 2014

A colleague of mine was working on a cube. The cube had a fact table that was also a dimension. It had 18 million rows of data. When my colleague tried to process the cube with that fact and dimension, he couldn’t. Both the full and the incremental process didn’t work. He got an error on processing the large dimension with a message of:   Exception calling "Process" with "1" argument(s): "File system error: A FileStore error from WriteFile occurred. Physical file: . Logical file: . . Errors in the OLAP storage engine: An error occurred while the 'RN' attribute of the 'YYYYY'...
no comments

Problem Connecting from Panorama to PowerPivot

Sunday, May 19, 2013

We installed Panorama Nova View Flash 6.2.5 and wanted to use it to connect to PowerPivot. While beginning the work, we couldn't connect to the PowerPivot files and would get an error message. My colleague Tomer Horev was in charge of SharePoint installation and also found the following solution. We understood what the problem was through the help of Panorama support. We tried to connect to the cube that's created for our PowerPivot file through the Management Studio. That meant connecting to the SSAS DB with the name of: http://servername/foldername/filename.xlsx ...

Power View on SSAS Multidimensional

Tuesday, December 11, 2012

Microsoft recently released a CTP of Power View on SSAS Multidimensional, (and yes, I know I'm a bit late writing about this, but I still wanted to give my two cents on it). So we're edging closer towards the point where Power View and Excel will be able to cover all of your viewer needs (or at least most of them :)). Years ago when I wrote about Report Builder on a cube and all the problems that that relationship created, I wondered when that would be fixed. Now that we have Power View, I'm glad that Microsoft is...
no comments

A Comparison between SQL Server 2012 BI Tools

Saturday, July 28, 2012

I have recently posted an article in Silicon India comparing SQL Server 2012 BI tools and means of development. I addressed there the tools in SQL Server 2012: SSRS, Report Builder 3.0, Power View, Tabular and Multidimensional Analysis Services.Though I tried to cover much ground in the article, I would still recommend some additional reading: A short comparison between Tabular mode vs. PowerPivot A more detailed comparison between Tabular mode vs. PowerPivot vs. Multidimensional SSAS ...

The Tabular Model in SQL Server 2012

Tuesday, July 3, 2012

This is a summary of a lecture given in the last BI User Group meeting in Israel by Mr. Itay Braun:   SSAS will give you better performance on top of a DWH of a few Terras (2+) rather than Tabular mode. That's because of the data summary and compression SSAS does to the data. Tabular is not necessarily faster than MOLAP.   Tabular mode is a new DB engine with 2 possible modes of interaction: 1.    Tabular Mode -      Column store -      In memory -      Compression (~1:3) -      All the data copied 2.    Direct SQL -      Queries translated into SQL running against the SQL DB -      Serves as Tabular mode's...
one comment

Free Lesson for SQL Server and SharePoint

Tuesday, June 12, 2012

Via BI/BPM - The SeeQueL, I have recently learned of a great new site I would like to share with you: MSBIAcademy. MSBIAcademy is a site created by Rob Kerr, SQL Server MVP and CTO at BlueGranite. The site currently offers lessons on: Excel, Integration Services, Data Warehouse Design, SQL Server, Mobile, SharePoint, Analysis Services (both Tabular and Multidimensional) and PowerView! Quite the impressive list. Most lessons are on the latest version of SQL Server, but guide lines given in them are true for earlier versions as well. I highly recommend you check out MSBIAcademy as in short lessons of...

Cascading Measure Values in a User Hierarchy in SSAS

Sunday, February 12, 2012

I had a new measure to add to my cube a new measure. My fact table up till now was with a monthly granularity. I assumed that I would have to define a scope in MDX for the intermediate period and the monthly period. I connected the fact to the year level in the Period dimension and got this message: If you select a non – key granularity attribute, the server will not be able to aggregate data properly unless you make sure that all other attributes are directly or indirectly related to it by specifying them as related attributes Now,...
one comment

Why are rows (still) missing from a SSAS cube?

Monday, September 19, 2011

Not too long ago my boss Yaniv got a telephone from one of our customers saying that he thought a cube was missing some values from it. The thing is that at first that didn't sound logical to us because usually we would get an error on that. We expected the process of the cube to fail, or something of that sort. But not this time. Now, there's a few reasons why there are rows missing from a cube as recently blogged by Richard Lees. But our reason was slightly different.We were using a view in the DSV. The...

Query Performance and Partition Scans in SSAS

Sunday, July 17, 2011

This blog is SUPER SUPER excited, because for the first time, after four years, we have a guest! I met Mr. Kobi Deutsch in the SQL Explore Convention held about two weeks ago. During a session we both took there, he mentioned something I wasn't aware and I thought maybe I'd bring it to you as well. So, I'm leaving the stage for Mr. Deutsch: Sometimes, when we check the MDX requests in the Profiler, we see that there is a partition that was scanned and loaded into memory although it is not suppose to be touched at all.How...

Error Processing a Cube: Key cannot be null. Parameter name: key

Wednesday, July 13, 2011

I recently opened a new project in SSAS 2008 R2. After finishing developing the cube, I deployed and processed it on the server. I got a really weird error message that meant, unfortunately enough, nothing to me: "Key cannot be null. Parameter name: key" So what's a girl to do? Well actually, I remember that every so often when I was developing a cube, I would have a problem with the data connection. The default I had defined for me when I opened a new connection was .Net Provider\SqlClient Data Provider. And somehow the default definition would always create an error...