Metric gathering and reporting system for identifying database performance and throughput problems
View Patent ↗A database back end system includes a monitoring server operable to poll a first database for a first query running on the first database and add the first query to a query list in a second database, and a reporting server operable to normalize the first query, analyze the second database to find a second query in the query list, wherein the second query is found based upon the normalized first query, and report the second query to a user, wherein the reporting is based upon the analyzing of the second database to find the second query.
1. A reporting server comprising:
a memory; and
a processor in communication with the memory and operable to:
normalize a variable of a first query running on a first database, wherein the first query is included in a query list in a second database;
analyze the second database to find a second query in the query list, wherein the second query is found based upon the normalized first query;
report the second query to a user, wherein the reporting is based upon the analyzing of the second database to find the second query; and
determine a first loading on a first database based upon a first frequency of occurrence of the second query and upon a first duration of the second query.
2. The reporting server of claim 1 , wherein in normalizing the variable of the first query, the processor is further operable to:
determine that a field of the first query includes a first value; and
replace the first value with a variable.
3. The reporting server of claim 1 , wherein the processor is further operable to:
analyze the second database to find a third query in the query list; and
report the third query to the user, wherein the reporting is based upon the analyzing of the second database to find the third query.
4. The reporting server of claim 3 , wherein the processor is further operable to:
rank the second and third queries based upon the first loading on the first database of the first query as compared to a second loading on the first database of the second query;
wherein reporting the second and third queries are in response to the ranking.
5. The reporting server of claim 4 , wherein the processor is further operable to:
determine the second loading based upon a second frequency of occurrence of the third query and upon a second duration of the third query;
wherein ranking the second and third queries is in response to determining the first and second loading.
6. The reporting server of claim 3 , wherein the second query locks a portion of the first database and the third query is a victim of the second query.
7. The reporting server of claim 6 , wherein the processor is further operable to:
determine a locking on the first database based upon a second frequency of occurrence of the third query following the second query.
8. The reporting server of claim 1 , wherein a monitoring server includes a first database management system that is associated with the first database.
9. The reporting server of claim 8 , wherein the first database management system is separate from a second database management system that is associated with the first database, and that operates to issue the first query on the first database.
10. A reporting server comprising:
a memory in communication with a processor;
wherein the processor is operable to:
normalize a variable of a first query running on a first database, wherein the first query is included in a query list in a second database, wherein in normalizing the first query the processor is further operable to determine that a field of the first query includes a first value, and replace the first value with a variable;
analyze the second database to find a second query in the query list, wherein the second query is found based upon the normalized first query;
report the second query to a user, wherein the reporting is based upon the analyzing of the second database to find the second query;
determine a first loading on a first database based upon a first frequency of occurrence of the second query and upon a first duration of the second query;
analyze the second database to find a third query in the query list; and
report the third query to the user, wherein the reporting is based upon the analyzing of the second database to find the third query.
11. The reporting server of claim 10 , wherein the processor is further operable to:
rank the second and third queries based upon the first loading on the first database of the first query as compared to a second loading on the first database of the second query;
wherein reporting the second and third queries are in response to the ranking.
12. The reporting server of claim 11 , wherein the processor is further operable to:
determine the second loading based upon a second frequency of occurrence of the third query and upon a second duration of the third query;
wherein ranking the second and third queries is in response to determining the first and second loading.
13. The reporting server of claim 10 , wherein the second query locks a portion of the first database and the third query is a victim of the second query.
14. The reporting server of claim 13 , wherein the processor is further operable to:
determine a locking on the first database based upon a second frequency of occurrence of the third query following the second query.
15. The reporting server of claim 10 , wherein a monitoring server includes a first database management system that is associated with the first database.
16. The reporting server of claim 15 , wherein the first database management system is separate from a second database management system that is associated with the first database, and that operates to issue the first query on the first database.
17. A reporting server comprising:
a memory; and
a processor in communication with the memory and operable to:
normalize a variable of a first query running on a first database, wherein the first query is included in a query list in a second database;
analyze the second database to find a second query in the query list, wherein the second query is found based upon the normalized first query;
report the second query to a user, wherein the reporting is based upon the analyzing of the second database to find the second query;
determine a first loading on a first database based upon a first frequency of occurrence of the second query and upon a first duration of the second query;
analyze the second database to find a third query in the query list; and
report the third query to the user, wherein the reporting is based upon the analyzing of the second database to find the third query;
wherein a monitoring server includes a first database management system that is associated with the first database.
18. The reporting server of claim 17 , wherein the processor is further operable to:
rank the second and third queries based upon the first loading on the first database of the first query as compared to a second loading on the first database of the second query;
wherein reporting the second and third queries are in response to the ranking.
19. The reporting server of claim 18 , wherein the processor is further operable to:
determine the second loading based upon a second frequency of occurrence of the third query and upon a second duration of the third query;
wherein ranking the second and third queries is in response to determining the first and second loading.
20. The reporting server of claim 19 , wherein the second query locks a portion of the first database and the third query is a victim of the second query.