Partitioned cubes and sparsity
When performance problems occur, one bottleneck is backing up the data on the hard drive. We can counter this by setting the saving policy. Depending on the selected setting, it is a trade-off between performance and security. With my suggestion I would like to defuse this tension.
With the SQL-Server from Microsoft it is possible to split tables and index on several hard disks. In this way, many more write and read operations can be executed simultaneously. This would make the backup faster during operation. In addition, the system is available faster after a restart. Depending on how this is implemented, backups could also be created and restored faster.
Functionality:
For each cube, a developer can decide whether to partition it. If yes, he chooses an entity for the partitioning. Depending on the available partitions, a script defines which entity elements are stored on the respective partition.
Example:
Our selected entity has 5 elements. These could be product areas. The product areas A, B and C will be written to partition 1. D and E are stored on the second partition.
If needed, more partitions can be added to scale the system.
Comments
-
Thank you for sharing your idea, @Nico Gerbrand. We appreciate the time and effort you put into crafting your suggestion, and we understand that it can be disappointing to hear that we won't be pursuing it at this time.
We are committed to delivering the best possible experience to our customers, and we must prioritize the features and enhancements that will have the most significant impact on your daily use of our software.
While we won't be moving forward with your suggestion, we want you to know that we value your input and appreciate your contribution to our community.We encourage you to continue submitting your ideas and suggestions in the future, as we are always open to hearing new perspectives and feedback.
0
