Dear Readers,
Something usefull with Vanilla v4 is the possibility to manage weight for requests, and prevent the request to be issued against the database – based on predefined rules – if the weight exceed the predefined limit.
What is the interest ?
Using FreeWebReport, user are able to build complex report that contain crosstab elements and various grouping strategy. Some user need “assistance” when it comes to build complex reports, and sometimes, putting too many element in a report is not effecient. Purpose is to stop the request a user may raise before it goes to the database if Bi admin think the request is too heavy (simple example : too many tables in the sql statment).
How does it works ?
Each table in the Metadata document is set with a predefined weight. We all understand its not a database admin feature, but more a datawarehouse features : tables have different behaviour – fact tables, dimension tables, aggregate table – different number of records and different index strategy. – Using Enterprise Services, each group of the Vanilla Group Table is set with a global limit. – When a user run a request, the Vanilla platform calculate the sum of weight for all the tables included in the requests. If the sum is superior to the limit set to the group, the request is stopped and a message raised in the interface.
FreeMetadata – Setting Weight for Tables
Enterprise Services – Setting limit for Groups
This feature is very flexible, and allow you to set a strategy outside of the database landscape. This can be an explanation, as we will see in next post in another audit & control interface, why a request can’t run for a specific group
Have Fun !
Patrick
Filed under: Enterprise Services, FreeMetadata, Vanilla, Vanilla4 | Leave a comment »