SQL Query Caches
The Cache mechanism in Canner Enterprise is one of the essential functions. Imagine your BI Team has Marketing, Sales, and Customer Support teams within the enterprise. Most of the information they need is similar, for example:
- Marketing: To check the sales performance of the previous week
- Sales Manager: To check the business status of the previous day
- Customer Support: Please take a look at last week's system report and customer feedback
So at this time, if there is no temporary storage mechanism, all ten Marketing members will query the previous week's results, and they will have to go to the database to re-fetch the data and calculate it before pulling the data to BI or CMS for viewing.
Usually, there is a delay between each recalculation, which may be minutes or hours. With the temporary storage mechanism of Canner Enterprise, these calculated data can present to the human source to be used later within a few milliseconds.
When querying SQL
When using SQL, avoid letting people who want to get the same data get it from the database every time. Our system provides a cache by default. When the system wants data, it will check whether it is cached. The system will read the most real-time data if you turn off the switch.
Currently, the system defaults the cache expiration time to 7 days (which can adjust according to usage requirements).
