Skip to main content
Solved

TimeXtender 6618.1 - reduction of Tabular model size

  • 10 May 2024
  • 3 replies
  • 88 views

Hi, 

One of the improvements of the that is stated for this update it says the following for the tabular model.


“We've improved the Tabular model generated by the Tabular semantic endpoint to have better efficiency and reduce the size of the model.”

 

Could you elaborate a bit more how it is more efficient and how you reduced the size? For us the size is especially important, since we have a 16gb limit with our ssas. Could you elaborate if you changed the encoding hints, since I do not assume you are changing any datatypes or something like that. Or did you guys mean that the processing of the tabular model has been improved, and the size it takes during processing has been reduced?

In any case, I wrote another question regarding Tabular model size, and DirectQuery mode. Maybe here the timextender team or anybody else can give guidelines / best practices to reduce the size of the Tabular model as much as possible.
 

 

3 replies

rvgfox
Rank
Userlevel 4
Badge +1

Hi @spenning that size reduction comes from a support ticket that we sent several months ago.

Bassically the reduction in this new version its don’t create a “Double” numeric field in the SSL model if the field it’s decimal. And setup the property of the model IsAvailableInMDX to false if the field is hidden.

To see more information about model siz reduction, see:

How to reduce the model size

Hope this helps

Ramon

S
Rank

Hi @rvgfox,

Thanks for the clarification, and for the article about reducing the model size, here is another good article about it btw (https://www.mssqltips.com/sqlservertip/5217/reduce-the-size-of-an-analysis-services-tabular-model-part-2/).

The IsAvailableInMDX is clear and sound, I'm just putting a link here so other people can also find out what this means exactly: 
(Chris Webb's BI Blog: How The New IsAvailableInMDX Property For Analysis Services Tabular Can Reduce Memory Usage And Speed Up Processing (crossjoin.co.uk)).

However, I'm not quite sure what you mean with that TX does not create a “Double” numeric field. I was reading this article about the different numeric data types in SSAS Tabular: Reduce the Size of an Analysis Services Tabular Model – Part 2

And I read another article you posted here: 

So, I assume based on the two articles that now instead of using a Double, the model will now use a Fixed Decimal Number / Currency?  

rvgfox
Rank
Userlevel 4
Badge +1

When you use decimal number and not double you get 40% reduction of size more and less.

Until this version the decimal number are converted to double allways.

Reply


Terms and ConditionsCookie settings