Is star schema is best or snowflake schema in Anaplan

Hello All, Can anyone suggest me which one is better between star schema and snowflake schema in Anaplan? I don't have much knowledge regarding both of these comparisons. Please suggest to me.

Accepted answers

All comments

LipChean_Soh

Hi,

In Anaplan, we don't refer to the Star or Snowflake schema, because these 2 schemas utilize the concept of a central Fact Table.

Instead we refer to the DISCO methodology https://community.anaplan.com/t5/Best-Practices/PLANS-This-Is-How-We-Model/ta-p/33530 , you can say the DISCO is like an enhanced Snowflake, it's enhanced because Anaplan stores transactional data where seen fit, and there could even be relationships between the multiple transactional data modules where seen fit.

However the common point i see between Star/Snowflake schema and DISCO is that Anaplan needs master data (aka List in Anaplan) to be populated first before the transactional data.

Thanks,

LipChean

rohanjoshi0894

With the Snowflake model, dimension analysis is easier. For example, “How many accounts or campaigns are online for a given advertiser?”

The Star schema model is useful for metrics analysis, such as “What is the revenue for a given customer?

Snowflake schemas offer the following benefits compared to normal star schemas:

Compatible with many OLAP database modeling tools: Certain OLAP database tools, which data scientists use for data analysis and modeling, are specifically designed to work snowflake data schemas.
Saves on data storage requirements: Normalizing the data that would typically be denormalized in a star schema can offer a tremendous reduction in disk space requirements. Essentially, this is because you're converting long strings of nonnumerical data (the information pertaining to descriptors and names) into numerical keys that are dramatically less taxing from a storage perspective.

Benefits of Star Schemas

Star schemas offer the following benefits:

Queries are simpler: Because all of the data connects through the fact table the multiple dimension tables are treated as one large table of information, and that makes queries simpler and easier to perform.
Easier business insights reporting: Star schemas simplify the process of pulling business reports like as-of-as and period-over-period reports.
Better-performing queries: By removing the bottlenecks of a highly normalized schema, query speed increases, and the performance of read-only commands improves.
Provides data to OLAP systems: OLAP (Online Analytical Processing) systems can use star schemas to build OLAP cubes.

I would go with Start schema, Want to know detailed information about Star Schema, Check this post.

Quick Links

Can you help?

Unanswered questions

Dimensionality Issue
Hi ALL, In my model, I have Need stored at a 'D3' RS Group level. I need to use this Need in another module at the G5 Location level. I currently have a mapping module where each G5 Location maps to a D3 RS Group. This Module uses D2 Role as dimension. but the line item I've to find the RS Group (Find D3 RS Group = 'FIND…
Formula to return Connection details...
I couldn't find any formula to do this, but I want a way to put on the page/grid the connection details. This is so I know what connection I'm in rather than going into Connections details to see it. Is there an XL3 formula to return this value?
Postman/Anaplan - message "404, Not found"
Hi all, I, as an Anaplan workspace administrator, am working together with a Fabric team to export data from Anaplan to Fabric via Anaplan API and Postman. We have a problem where all Anaplan exports are visible in Postman but when trying to connect to SOME of them, we get message "404, Not found". Below screenshot showing…