Recommendation : 1. Reduce the impact of data from its storage and access
Have the different data access solutions (queries, triggers, stored procedures) been tested ?
Data
C People
B Planet
B Prosperity
Difficulty
N/A
Priority
/
Récurrence
/
Tests
Are the performances of the different solutions (triggers, stored procedures, queries) known?
Precisions
The different methods of accessing data provided by DBMS engines can produce different resource consumption for a similar result. Among these solutions, queries, stored procedures, triggers should be evaluated to determine the best fit for each use, which would reduce resource consumption.
Additional elements
Rule for assessing the level of compliance of the criterion
0 / 0
Life cycle
Réalisation
19 other criteria related to the recommendation: Reduce the impact of data from its storage and access
Data
Is the number of requests kept to a minimum (no looping) ?
Data
Are the slow query detection thresholds set effectively ?
Data processing
Does regulated data (personal, health, financial) comply with the recommendations for structuring these categories of data ?
security
Is sensitive user data secure ?
Data processing
Does the API provide limits, filters and the list of fields to return ?
Data processing
Is the data collected really useful ?
Data processing
Is sensitive data collected ?
Data processing
Does the data have an expiration date when it is deleted ?
Data
Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?
Data
Is frequently accessed data available in RAM ?
Data
Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?
Data
Are EXPLAIN clauses used on "Slow queries" to optimize indexes ?
Data
Is a NoSql solution more efficient than its relational equivalent ?
Data
Is an alternative to the relational model being considered ?
Data
Are database indexes consistent with operations ?
Data
Is the removal of obsolete data being managed ?
Data
Can data be backed up incrementally ?
Data
Do implemented queries use joins rather than multiple queries ?
Data
Is an alternative to SQL queries used when possible (local storage or similar) ?