What is 'Log Memory' in Query Store 2017












2















In SQL 2017 there is a new execution metric, 'Log memory' other than that it was added in 2017 I am not finding anything about it.



Execution metric: (SQL 2017)




CPU time, Duration, Execution Count, Logical Reads, Logical writes, Memory consumption, Physical Reads, CLR time, Degree of Parallelism (DOP), Row count, Log memory, TempDB memory, and Wait times




I believe I understand what all the other metrics are and why I might care.



I ran all the metrics for the top 5 resource consuming queries, during several specific periods. I recorded and now I am examining the results. I know the (very large) values for 'Log memory' are in KB's.



What exactly is the metric 'Log memory'?










share|improve this question























  • I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

    – James Jenkins
    9 hours ago
















2















In SQL 2017 there is a new execution metric, 'Log memory' other than that it was added in 2017 I am not finding anything about it.



Execution metric: (SQL 2017)




CPU time, Duration, Execution Count, Logical Reads, Logical writes, Memory consumption, Physical Reads, CLR time, Degree of Parallelism (DOP), Row count, Log memory, TempDB memory, and Wait times




I believe I understand what all the other metrics are and why I might care.



I ran all the metrics for the top 5 resource consuming queries, during several specific periods. I recorded and now I am examining the results. I know the (very large) values for 'Log memory' are in KB's.



What exactly is the metric 'Log memory'?










share|improve this question























  • I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

    – James Jenkins
    9 hours ago














2












2








2


1






In SQL 2017 there is a new execution metric, 'Log memory' other than that it was added in 2017 I am not finding anything about it.



Execution metric: (SQL 2017)




CPU time, Duration, Execution Count, Logical Reads, Logical writes, Memory consumption, Physical Reads, CLR time, Degree of Parallelism (DOP), Row count, Log memory, TempDB memory, and Wait times




I believe I understand what all the other metrics are and why I might care.



I ran all the metrics for the top 5 resource consuming queries, during several specific periods. I recorded and now I am examining the results. I know the (very large) values for 'Log memory' are in KB's.



What exactly is the metric 'Log memory'?










share|improve this question














In SQL 2017 there is a new execution metric, 'Log memory' other than that it was added in 2017 I am not finding anything about it.



Execution metric: (SQL 2017)




CPU time, Duration, Execution Count, Logical Reads, Logical writes, Memory consumption, Physical Reads, CLR time, Degree of Parallelism (DOP), Row count, Log memory, TempDB memory, and Wait times




I believe I understand what all the other metrics are and why I might care.



I ran all the metrics for the top 5 resource consuming queries, during several specific periods. I recorded and now I am examining the results. I know the (very large) values for 'Log memory' are in KB's.



What exactly is the metric 'Log memory'?







sql-server sql-server-2017 query-store






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 10 hours ago









James JenkinsJames Jenkins

1,81121941




1,81121941













  • I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

    – James Jenkins
    9 hours ago



















  • I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

    – James Jenkins
    9 hours ago

















I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

– James Jenkins
9 hours ago





I found a similar unanswered question on SO MSSQL - Log Memory Used - Query Store

– James Jenkins
9 hours ago










2 Answers
2






active

oldest

votes


















5














If we look at the documentation for the underlying object, sys.query_store_runtime_stats, we'll see it has the following descriptions:





  • avg_log_bytes_used - Average number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
    Note: Azure SQL Data Warehouse will always return zero (0).


  • last_log_bytes_used - Number of bytes in the database log used by the last execution of the query plan, within the aggregation interval. Applies only to Azure SQL Database.
    Note: Azure SQL Data Warehouse will always return zero (0).


  • min_log_bytes_used - Minimum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
    Note: Azure SQL Data Warehouse will always return zero (0).


  • max_log_bytes_used - Maximum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
    Note: Azure SQL Data Warehouse will always return zero (0).


  • stdev_log_bytes_used - Standard deviation of the number of bytes in the database log used by a query plan, within the aggregation interval. Applies only to Azure SQL Database.
    Note: Azure SQL Data Warehouse will always return zero (0).






share|improve this answer































    1














    I think LowlyDBA's answer covers what the metrics actually mean. This answer is just an additional clarifying point.



    It appears the documentation is inaccurate with regards to "Applies only to Azure SQL Database". Maybe this is an old note in the docs from before those columns made it into the on-prem product, but it is easy to get data in those columns on SQL Server 2017 Developer Edition on my laptop.



    Create a database:



    USE [master];
    GO

    CREATE DATABASE [231682];
    GO


    Enable Query Store with very impractical settings:



    ALTER DATABASE [231682] SET QUERY_STORE = ON (INTERVAL_LENGTH_MINUTES = 1);


    Do something that will generate some transaction log usage:



    USE [231682];

    CREATE TABLE dbo.Junk
    (
    Id INT NOT NULL,
    MoreJunk NVARCHAR(MAX) NOT NULL
    );

    INSERT INTO dbo.Junk
    (Id, MoreJunk)
    SELECT TOP 1000
    m.message_id, m.[text]
    FROM sys.messages m;


    Force flush to disk in case it hasn't happened yet:



    EXEC sp_query_store_flush_db;


    Voila:



    SELECT 
    qsrs.avg_log_bytes_used,
    qsrs.last_log_bytes_used,
    qsrs.min_log_bytes_used,
    qsrs.max_log_bytes_used,
    qsrs.stdev_log_bytes_used
    FROM sys.query_store_runtime_stats qsrs
    WHERE qsrs.avg_log_bytes_used > 0;


    screenshot of results with non-zero data






    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%2f231682%2fwhat-is-log-memory-in-query-store-2017%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









      5














      If we look at the documentation for the underlying object, sys.query_store_runtime_stats, we'll see it has the following descriptions:





      • avg_log_bytes_used - Average number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
        Note: Azure SQL Data Warehouse will always return zero (0).


      • last_log_bytes_used - Number of bytes in the database log used by the last execution of the query plan, within the aggregation interval. Applies only to Azure SQL Database.
        Note: Azure SQL Data Warehouse will always return zero (0).


      • min_log_bytes_used - Minimum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
        Note: Azure SQL Data Warehouse will always return zero (0).


      • max_log_bytes_used - Maximum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
        Note: Azure SQL Data Warehouse will always return zero (0).


      • stdev_log_bytes_used - Standard deviation of the number of bytes in the database log used by a query plan, within the aggregation interval. Applies only to Azure SQL Database.
        Note: Azure SQL Data Warehouse will always return zero (0).






      share|improve this answer




























        5














        If we look at the documentation for the underlying object, sys.query_store_runtime_stats, we'll see it has the following descriptions:





        • avg_log_bytes_used - Average number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
          Note: Azure SQL Data Warehouse will always return zero (0).


        • last_log_bytes_used - Number of bytes in the database log used by the last execution of the query plan, within the aggregation interval. Applies only to Azure SQL Database.
          Note: Azure SQL Data Warehouse will always return zero (0).


        • min_log_bytes_used - Minimum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
          Note: Azure SQL Data Warehouse will always return zero (0).


        • max_log_bytes_used - Maximum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
          Note: Azure SQL Data Warehouse will always return zero (0).


        • stdev_log_bytes_used - Standard deviation of the number of bytes in the database log used by a query plan, within the aggregation interval. Applies only to Azure SQL Database.
          Note: Azure SQL Data Warehouse will always return zero (0).






        share|improve this answer


























          5












          5








          5







          If we look at the documentation for the underlying object, sys.query_store_runtime_stats, we'll see it has the following descriptions:





          • avg_log_bytes_used - Average number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • last_log_bytes_used - Number of bytes in the database log used by the last execution of the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • min_log_bytes_used - Minimum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • max_log_bytes_used - Maximum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • stdev_log_bytes_used - Standard deviation of the number of bytes in the database log used by a query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).






          share|improve this answer













          If we look at the documentation for the underlying object, sys.query_store_runtime_stats, we'll see it has the following descriptions:





          • avg_log_bytes_used - Average number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • last_log_bytes_used - Number of bytes in the database log used by the last execution of the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • min_log_bytes_used - Minimum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • max_log_bytes_used - Maximum number of bytes in the database log used by the query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).


          • stdev_log_bytes_used - Standard deviation of the number of bytes in the database log used by a query plan, within the aggregation interval. Applies only to Azure SQL Database.
            Note: Azure SQL Data Warehouse will always return zero (0).







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 9 hours ago









          LowlyDBALowlyDBA

          7,13252542




          7,13252542

























              1














              I think LowlyDBA's answer covers what the metrics actually mean. This answer is just an additional clarifying point.



              It appears the documentation is inaccurate with regards to "Applies only to Azure SQL Database". Maybe this is an old note in the docs from before those columns made it into the on-prem product, but it is easy to get data in those columns on SQL Server 2017 Developer Edition on my laptop.



              Create a database:



              USE [master];
              GO

              CREATE DATABASE [231682];
              GO


              Enable Query Store with very impractical settings:



              ALTER DATABASE [231682] SET QUERY_STORE = ON (INTERVAL_LENGTH_MINUTES = 1);


              Do something that will generate some transaction log usage:



              USE [231682];

              CREATE TABLE dbo.Junk
              (
              Id INT NOT NULL,
              MoreJunk NVARCHAR(MAX) NOT NULL
              );

              INSERT INTO dbo.Junk
              (Id, MoreJunk)
              SELECT TOP 1000
              m.message_id, m.[text]
              FROM sys.messages m;


              Force flush to disk in case it hasn't happened yet:



              EXEC sp_query_store_flush_db;


              Voila:



              SELECT 
              qsrs.avg_log_bytes_used,
              qsrs.last_log_bytes_used,
              qsrs.min_log_bytes_used,
              qsrs.max_log_bytes_used,
              qsrs.stdev_log_bytes_used
              FROM sys.query_store_runtime_stats qsrs
              WHERE qsrs.avg_log_bytes_used > 0;


              screenshot of results with non-zero data






              share|improve this answer




























                1














                I think LowlyDBA's answer covers what the metrics actually mean. This answer is just an additional clarifying point.



                It appears the documentation is inaccurate with regards to "Applies only to Azure SQL Database". Maybe this is an old note in the docs from before those columns made it into the on-prem product, but it is easy to get data in those columns on SQL Server 2017 Developer Edition on my laptop.



                Create a database:



                USE [master];
                GO

                CREATE DATABASE [231682];
                GO


                Enable Query Store with very impractical settings:



                ALTER DATABASE [231682] SET QUERY_STORE = ON (INTERVAL_LENGTH_MINUTES = 1);


                Do something that will generate some transaction log usage:



                USE [231682];

                CREATE TABLE dbo.Junk
                (
                Id INT NOT NULL,
                MoreJunk NVARCHAR(MAX) NOT NULL
                );

                INSERT INTO dbo.Junk
                (Id, MoreJunk)
                SELECT TOP 1000
                m.message_id, m.[text]
                FROM sys.messages m;


                Force flush to disk in case it hasn't happened yet:



                EXEC sp_query_store_flush_db;


                Voila:



                SELECT 
                qsrs.avg_log_bytes_used,
                qsrs.last_log_bytes_used,
                qsrs.min_log_bytes_used,
                qsrs.max_log_bytes_used,
                qsrs.stdev_log_bytes_used
                FROM sys.query_store_runtime_stats qsrs
                WHERE qsrs.avg_log_bytes_used > 0;


                screenshot of results with non-zero data






                share|improve this answer


























                  1












                  1








                  1







                  I think LowlyDBA's answer covers what the metrics actually mean. This answer is just an additional clarifying point.



                  It appears the documentation is inaccurate with regards to "Applies only to Azure SQL Database". Maybe this is an old note in the docs from before those columns made it into the on-prem product, but it is easy to get data in those columns on SQL Server 2017 Developer Edition on my laptop.



                  Create a database:



                  USE [master];
                  GO

                  CREATE DATABASE [231682];
                  GO


                  Enable Query Store with very impractical settings:



                  ALTER DATABASE [231682] SET QUERY_STORE = ON (INTERVAL_LENGTH_MINUTES = 1);


                  Do something that will generate some transaction log usage:



                  USE [231682];

                  CREATE TABLE dbo.Junk
                  (
                  Id INT NOT NULL,
                  MoreJunk NVARCHAR(MAX) NOT NULL
                  );

                  INSERT INTO dbo.Junk
                  (Id, MoreJunk)
                  SELECT TOP 1000
                  m.message_id, m.[text]
                  FROM sys.messages m;


                  Force flush to disk in case it hasn't happened yet:



                  EXEC sp_query_store_flush_db;


                  Voila:



                  SELECT 
                  qsrs.avg_log_bytes_used,
                  qsrs.last_log_bytes_used,
                  qsrs.min_log_bytes_used,
                  qsrs.max_log_bytes_used,
                  qsrs.stdev_log_bytes_used
                  FROM sys.query_store_runtime_stats qsrs
                  WHERE qsrs.avg_log_bytes_used > 0;


                  screenshot of results with non-zero data






                  share|improve this answer













                  I think LowlyDBA's answer covers what the metrics actually mean. This answer is just an additional clarifying point.



                  It appears the documentation is inaccurate with regards to "Applies only to Azure SQL Database". Maybe this is an old note in the docs from before those columns made it into the on-prem product, but it is easy to get data in those columns on SQL Server 2017 Developer Edition on my laptop.



                  Create a database:



                  USE [master];
                  GO

                  CREATE DATABASE [231682];
                  GO


                  Enable Query Store with very impractical settings:



                  ALTER DATABASE [231682] SET QUERY_STORE = ON (INTERVAL_LENGTH_MINUTES = 1);


                  Do something that will generate some transaction log usage:



                  USE [231682];

                  CREATE TABLE dbo.Junk
                  (
                  Id INT NOT NULL,
                  MoreJunk NVARCHAR(MAX) NOT NULL
                  );

                  INSERT INTO dbo.Junk
                  (Id, MoreJunk)
                  SELECT TOP 1000
                  m.message_id, m.[text]
                  FROM sys.messages m;


                  Force flush to disk in case it hasn't happened yet:



                  EXEC sp_query_store_flush_db;


                  Voila:



                  SELECT 
                  qsrs.avg_log_bytes_used,
                  qsrs.last_log_bytes_used,
                  qsrs.min_log_bytes_used,
                  qsrs.max_log_bytes_used,
                  qsrs.stdev_log_bytes_used
                  FROM sys.query_store_runtime_stats qsrs
                  WHERE qsrs.avg_log_bytes_used > 0;


                  screenshot of results with non-zero data







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 3 hours ago









                  jadarnel27jadarnel27

                  6,27012038




                  6,27012038






























                      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%2f231682%2fwhat-is-log-memory-in-query-store-2017%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

                      Knooppunt Holsloot

                      Altaar (religie)

                      Gregoriusmis