how to figure out a query's frequency?












0















how to calculate a query's frequency ? I doubt that some query is very often,I want to know its pqs,can any body tell me ? I have tried using general log,is there any tool to figure out ?










share|improve this question














bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    how to calculate a query's frequency ? I doubt that some query is very often,I want to know its pqs,can any body tell me ? I have tried using general log,is there any tool to figure out ?










    share|improve this question














    bumped to the homepage by Community 9 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      how to calculate a query's frequency ? I doubt that some query is very often,I want to know its pqs,can any body tell me ? I have tried using general log,is there any tool to figure out ?










      share|improve this question














      how to calculate a query's frequency ? I doubt that some query is very often,I want to know its pqs,can any body tell me ? I have tried using general log,is there any tool to figure out ?







      mysql






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 '17 at 10:00









      LawrenceLiLawrenceLi

      91110




      91110





      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          Sp_blitzcache will give you this information.



          Have a look: https://www.brentozar.com/blitzcache/



          In the past, this has helped me find queries running thousands of times/minute that were having parameter sniffing issues, meaning the same query was being recompiled each time.






          share|improve this answer































            0














            Plan A: Turn on the "general log" and use pt-query-digest to analyze the log.



            Plan B: Set long_query_time = 0 and turn on the slowlog. Then use pt-query-digest to analyze the log.



            Caution: In either case, disk will fill up fast.



            With the slowlog you get a lot of other information -- useful if you are concerned about what is bogging down the system. That is a different question than 'frequency'; it is frequency * avg execution time.






            share|improve this answer























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "182"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f159805%2fhow-to-figure-out-a-querys-frequency%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Sp_blitzcache will give you this information.



              Have a look: https://www.brentozar.com/blitzcache/



              In the past, this has helped me find queries running thousands of times/minute that were having parameter sniffing issues, meaning the same query was being recompiled each time.






              share|improve this answer




























                0














                Sp_blitzcache will give you this information.



                Have a look: https://www.brentozar.com/blitzcache/



                In the past, this has helped me find queries running thousands of times/minute that were having parameter sniffing issues, meaning the same query was being recompiled each time.






                share|improve this answer


























                  0












                  0








                  0







                  Sp_blitzcache will give you this information.



                  Have a look: https://www.brentozar.com/blitzcache/



                  In the past, this has helped me find queries running thousands of times/minute that were having parameter sniffing issues, meaning the same query was being recompiled each time.






                  share|improve this answer













                  Sp_blitzcache will give you this information.



                  Have a look: https://www.brentozar.com/blitzcache/



                  In the past, this has helped me find queries running thousands of times/minute that were having parameter sniffing issues, meaning the same query was being recompiled each time.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 3 '17 at 11:16









                  PeterPeter

                  7431726




                  7431726

























                      0














                      Plan A: Turn on the "general log" and use pt-query-digest to analyze the log.



                      Plan B: Set long_query_time = 0 and turn on the slowlog. Then use pt-query-digest to analyze the log.



                      Caution: In either case, disk will fill up fast.



                      With the slowlog you get a lot of other information -- useful if you are concerned about what is bogging down the system. That is a different question than 'frequency'; it is frequency * avg execution time.






                      share|improve this answer




























                        0














                        Plan A: Turn on the "general log" and use pt-query-digest to analyze the log.



                        Plan B: Set long_query_time = 0 and turn on the slowlog. Then use pt-query-digest to analyze the log.



                        Caution: In either case, disk will fill up fast.



                        With the slowlog you get a lot of other information -- useful if you are concerned about what is bogging down the system. That is a different question than 'frequency'; it is frequency * avg execution time.






                        share|improve this answer


























                          0












                          0








                          0







                          Plan A: Turn on the "general log" and use pt-query-digest to analyze the log.



                          Plan B: Set long_query_time = 0 and turn on the slowlog. Then use pt-query-digest to analyze the log.



                          Caution: In either case, disk will fill up fast.



                          With the slowlog you get a lot of other information -- useful if you are concerned about what is bogging down the system. That is a different question than 'frequency'; it is frequency * avg execution time.






                          share|improve this answer













                          Plan A: Turn on the "general log" and use pt-query-digest to analyze the log.



                          Plan B: Set long_query_time = 0 and turn on the slowlog. Then use pt-query-digest to analyze the log.



                          Caution: In either case, disk will fill up fast.



                          With the slowlog you get a lot of other information -- useful if you are concerned about what is bogging down the system. That is a different question than 'frequency'; it is frequency * avg execution time.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 4 '17 at 5:29









                          Rick JamesRick James

                          43k22259




                          43k22259






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Database Administrators Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f159805%2fhow-to-figure-out-a-querys-frequency%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              SQL Server 17 - Attemping to backup to remote NAS but Access is denied

                              Always On Availability groups resolving state after failover - Remote harden of transaction...

                              Restoring from pg_dump with foreign key constraints