If a VARCHAR(MAX) column is included in an index, is the entire value always stored in the index page(s)? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Why does sql server prefer the nonclustered index over the clustered index?varchar performance impactAren't two writes required to update a clustered index recordChanging TEXT to VARCHARUsing wildcards in a like statement on an unindexed VARCHAR(MAX) column with more than 1 million recordsStorage size for varchar length in RedshiftWhy SQL Server has 900 byte index size limitSlow DELETEs of LOB data in SQL ServerHow do I compare large stored procedures?What are the current best practices concerning varchar sizing in SQL Server?Convert varbinary(max) with CONVERT(nvarchar/varchar(max) ,value,0) gives no logic results

How do I stop a creek from eroding my steep embankment?

Do jazz musicians improvise on the parent scale in addition to the chord-scales?

Can melee weapons be used to deliver Contact Poisons?

Circuit to "zoom in" on mV fluctuations of a DC signal?

Maximum summed powersets with non-adjacent items

Wu formula for manifolds with boundary

Is grep documentation wrong?

What does "lightly crushed" mean for cardamon pods?

Can an alien society believe that their star system is the universe?

What is the longest distance a player character can jump in one leap?

Is there any way for the UK Prime Minister to make a motion directly dependent on Government confidence?

What's the meaning of "fortified infraction restraint"?

Can you use the Shield Master feat to shove someone before you make an attack by using a Readied action?

Irreducible of finite Krull dimension implies quasi-compact?

How to show element name in portuguese using elements package?

Why wasn't DOSKEY integrated with COMMAND.COM?

Using audio cues to encourage good posture

What is the meaning of the simile “quick as silk”?

Delete nth line from bottom

An adverb for when you're not exaggerating

Did MS DOS itself ever use blinking text?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

How to Make a Beautiful Stacked 3D Plot

Dating a Former Employee



If a VARCHAR(MAX) column is included in an index, is the entire value always stored in the index page(s)?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Why does sql server prefer the nonclustered index over the clustered index?varchar performance impactAren't two writes required to update a clustered index recordChanging TEXT to VARCHARUsing wildcards in a like statement on an unindexed VARCHAR(MAX) column with more than 1 million recordsStorage size for varchar length in RedshiftWhy SQL Server has 900 byte index size limitSlow DELETEs of LOB data in SQL ServerHow do I compare large stored procedures?What are the current best practices concerning varchar sizing in SQL Server?Convert varbinary(max) with CONVERT(nvarchar/varchar(max) ,value,0) gives no logic results



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I'm asking this out of curiosity, being inspired by this question.



We know that VARCHAR(MAX) values longer than 8000 bytes are not stored in rows, but in separate LOB pages. Subsequently retrieving a row with such value requires two or more logical IO operations (essentially, one more than otherwise would theoretically be necessary).



We can add a VARCHAR(MAX) column to a unique index, as demonstrated in the linked question. If this column has values that exceed 8000 bytes in length, would such values still be stored "inline" in the index leaf pages, or would they also be moved to LOB pages?










share|improve this question




























    2















    I'm asking this out of curiosity, being inspired by this question.



    We know that VARCHAR(MAX) values longer than 8000 bytes are not stored in rows, but in separate LOB pages. Subsequently retrieving a row with such value requires two or more logical IO operations (essentially, one more than otherwise would theoretically be necessary).



    We can add a VARCHAR(MAX) column to a unique index, as demonstrated in the linked question. If this column has values that exceed 8000 bytes in length, would such values still be stored "inline" in the index leaf pages, or would they also be moved to LOB pages?










    share|improve this question
























      2












      2








      2








      I'm asking this out of curiosity, being inspired by this question.



      We know that VARCHAR(MAX) values longer than 8000 bytes are not stored in rows, but in separate LOB pages. Subsequently retrieving a row with such value requires two or more logical IO operations (essentially, one more than otherwise would theoretically be necessary).



      We can add a VARCHAR(MAX) column to a unique index, as demonstrated in the linked question. If this column has values that exceed 8000 bytes in length, would such values still be stored "inline" in the index leaf pages, or would they also be moved to LOB pages?










      share|improve this question














      I'm asking this out of curiosity, being inspired by this question.



      We know that VARCHAR(MAX) values longer than 8000 bytes are not stored in rows, but in separate LOB pages. Subsequently retrieving a row with such value requires two or more logical IO operations (essentially, one more than otherwise would theoretically be necessary).



      We can add a VARCHAR(MAX) column to a unique index, as demonstrated in the linked question. If this column has values that exceed 8000 bytes in length, would such values still be stored "inline" in the index leaf pages, or would they also be moved to LOB pages?







      sql-server varchar






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 hours ago









      mustacciomustaccio

      10.1k72240




      10.1k72240




















          1 Answer
          1






          active

          oldest

          votes


















          3














          Values that exceed 8000 bytes cannot be stored "inline". They are stored on LOB pages. You can see this with sys.dm_db_index_physical_stats. Start with a simple table:



          DROP TABLE IF EXISTS #LOB_FOR_ME;

          CREATE TABLE #LOB_FOR_ME (
          ID BIGINT,
          MAX_VERNON_WAS_HERE VARCHAR(MAX)
          );

          CREATE INDEX IX ON #LOB_FOR_ME (ID) INCLUDE (MAX_VERNON_WAS_HERE);


          Now insert some rows with values that take 8000 bytes for the VARCHAR(MAX) column and check out the DMF:



          INSERT INTO #LOB_FOR_ME
          SELECT 1, REPLICATE('Z', 8000)
          FROM master..spt_values;

          SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
          FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


          There are no LOB pages in the index:



          ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
          ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
          ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
          ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2540 ║ 2540 ║
          ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2540 ║
          ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
          ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


          But if I add rows with values that take 8001 bytes:



          INSERT INTO #LOB_FOR_ME
          SELECT 2, REPLICATE(CAST('Z' AS VARCHAR(MAX)), 8001)
          FROM master..spt_values;

          SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
          FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


          Now I have 1 LOB page in the index for every row that I just inserted:



          ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
          ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
          ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
          ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2556 ║ 5080 ║
          ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2556 ║
          ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
          ║ 0 ║ NONCLUSTERED INDEX ║ LOB_DATA ║ 2540 ║ 2540 ║
          ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


          You can also see this with SET STATISTICS IO ON; and the right query. Consider the following query that only looks at rows with 8000 bytes:



          SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
          FROM #LOB_FOR_ME
          WHERE ID = 1;


          Results upon executing:




          Scan count 1, logical reads 2560, physical reads 0, read-ahead reads
          0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.




          If I instead query the rows with 8001 bytes:



          SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
          FROM #LOB_FOR_ME
          WHERE ID = 2;


          Now I see lob reads:




          Scan count 1, logical reads 20, physical reads 0, read-ahead reads 0,
          lob logical reads 5080, lob physical reads 0, lob read-ahead reads 0.







          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%2f235102%2fif-a-varcharmax-column-is-included-in-an-index-is-the-entire-value-always-sto%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            Values that exceed 8000 bytes cannot be stored "inline". They are stored on LOB pages. You can see this with sys.dm_db_index_physical_stats. Start with a simple table:



            DROP TABLE IF EXISTS #LOB_FOR_ME;

            CREATE TABLE #LOB_FOR_ME (
            ID BIGINT,
            MAX_VERNON_WAS_HERE VARCHAR(MAX)
            );

            CREATE INDEX IX ON #LOB_FOR_ME (ID) INCLUDE (MAX_VERNON_WAS_HERE);


            Now insert some rows with values that take 8000 bytes for the VARCHAR(MAX) column and check out the DMF:



            INSERT INTO #LOB_FOR_ME
            SELECT 1, REPLICATE('Z', 8000)
            FROM master..spt_values;

            SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
            FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


            There are no LOB pages in the index:



            ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
            ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
            ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
            ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2540 ║ 2540 ║
            ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2540 ║
            ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
            ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


            But if I add rows with values that take 8001 bytes:



            INSERT INTO #LOB_FOR_ME
            SELECT 2, REPLICATE(CAST('Z' AS VARCHAR(MAX)), 8001)
            FROM master..spt_values;

            SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
            FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


            Now I have 1 LOB page in the index for every row that I just inserted:



            ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
            ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
            ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
            ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2556 ║ 5080 ║
            ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2556 ║
            ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
            ║ 0 ║ NONCLUSTERED INDEX ║ LOB_DATA ║ 2540 ║ 2540 ║
            ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


            You can also see this with SET STATISTICS IO ON; and the right query. Consider the following query that only looks at rows with 8000 bytes:



            SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
            FROM #LOB_FOR_ME
            WHERE ID = 1;


            Results upon executing:




            Scan count 1, logical reads 2560, physical reads 0, read-ahead reads
            0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.




            If I instead query the rows with 8001 bytes:



            SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
            FROM #LOB_FOR_ME
            WHERE ID = 2;


            Now I see lob reads:




            Scan count 1, logical reads 20, physical reads 0, read-ahead reads 0,
            lob logical reads 5080, lob physical reads 0, lob read-ahead reads 0.







            share|improve this answer



























              3














              Values that exceed 8000 bytes cannot be stored "inline". They are stored on LOB pages. You can see this with sys.dm_db_index_physical_stats. Start with a simple table:



              DROP TABLE IF EXISTS #LOB_FOR_ME;

              CREATE TABLE #LOB_FOR_ME (
              ID BIGINT,
              MAX_VERNON_WAS_HERE VARCHAR(MAX)
              );

              CREATE INDEX IX ON #LOB_FOR_ME (ID) INCLUDE (MAX_VERNON_WAS_HERE);


              Now insert some rows with values that take 8000 bytes for the VARCHAR(MAX) column and check out the DMF:



              INSERT INTO #LOB_FOR_ME
              SELECT 1, REPLICATE('Z', 8000)
              FROM master..spt_values;

              SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
              FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


              There are no LOB pages in the index:



              ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
              ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
              ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
              ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2540 ║ 2540 ║
              ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2540 ║
              ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
              ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


              But if I add rows with values that take 8001 bytes:



              INSERT INTO #LOB_FOR_ME
              SELECT 2, REPLICATE(CAST('Z' AS VARCHAR(MAX)), 8001)
              FROM master..spt_values;

              SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
              FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


              Now I have 1 LOB page in the index for every row that I just inserted:



              ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
              ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
              ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
              ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2556 ║ 5080 ║
              ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2556 ║
              ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
              ║ 0 ║ NONCLUSTERED INDEX ║ LOB_DATA ║ 2540 ║ 2540 ║
              ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


              You can also see this with SET STATISTICS IO ON; and the right query. Consider the following query that only looks at rows with 8000 bytes:



              SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
              FROM #LOB_FOR_ME
              WHERE ID = 1;


              Results upon executing:




              Scan count 1, logical reads 2560, physical reads 0, read-ahead reads
              0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.




              If I instead query the rows with 8001 bytes:



              SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
              FROM #LOB_FOR_ME
              WHERE ID = 2;


              Now I see lob reads:




              Scan count 1, logical reads 20, physical reads 0, read-ahead reads 0,
              lob logical reads 5080, lob physical reads 0, lob read-ahead reads 0.







              share|improve this answer

























                3












                3








                3







                Values that exceed 8000 bytes cannot be stored "inline". They are stored on LOB pages. You can see this with sys.dm_db_index_physical_stats. Start with a simple table:



                DROP TABLE IF EXISTS #LOB_FOR_ME;

                CREATE TABLE #LOB_FOR_ME (
                ID BIGINT,
                MAX_VERNON_WAS_HERE VARCHAR(MAX)
                );

                CREATE INDEX IX ON #LOB_FOR_ME (ID) INCLUDE (MAX_VERNON_WAS_HERE);


                Now insert some rows with values that take 8000 bytes for the VARCHAR(MAX) column and check out the DMF:



                INSERT INTO #LOB_FOR_ME
                SELECT 1, REPLICATE('Z', 8000)
                FROM master..spt_values;

                SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
                FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


                There are no LOB pages in the index:



                ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
                ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
                ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
                ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2540 ║ 2540 ║
                ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2540 ║
                ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
                ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


                But if I add rows with values that take 8001 bytes:



                INSERT INTO #LOB_FOR_ME
                SELECT 2, REPLICATE(CAST('Z' AS VARCHAR(MAX)), 8001)
                FROM master..spt_values;

                SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
                FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


                Now I have 1 LOB page in the index for every row that I just inserted:



                ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
                ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
                ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
                ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2556 ║ 5080 ║
                ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2556 ║
                ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
                ║ 0 ║ NONCLUSTERED INDEX ║ LOB_DATA ║ 2540 ║ 2540 ║
                ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


                You can also see this with SET STATISTICS IO ON; and the right query. Consider the following query that only looks at rows with 8000 bytes:



                SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
                FROM #LOB_FOR_ME
                WHERE ID = 1;


                Results upon executing:




                Scan count 1, logical reads 2560, physical reads 0, read-ahead reads
                0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.




                If I instead query the rows with 8001 bytes:



                SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
                FROM #LOB_FOR_ME
                WHERE ID = 2;


                Now I see lob reads:




                Scan count 1, logical reads 20, physical reads 0, read-ahead reads 0,
                lob logical reads 5080, lob physical reads 0, lob read-ahead reads 0.







                share|improve this answer













                Values that exceed 8000 bytes cannot be stored "inline". They are stored on LOB pages. You can see this with sys.dm_db_index_physical_stats. Start with a simple table:



                DROP TABLE IF EXISTS #LOB_FOR_ME;

                CREATE TABLE #LOB_FOR_ME (
                ID BIGINT,
                MAX_VERNON_WAS_HERE VARCHAR(MAX)
                );

                CREATE INDEX IX ON #LOB_FOR_ME (ID) INCLUDE (MAX_VERNON_WAS_HERE);


                Now insert some rows with values that take 8000 bytes for the VARCHAR(MAX) column and check out the DMF:



                INSERT INTO #LOB_FOR_ME
                SELECT 1, REPLICATE('Z', 8000)
                FROM master..spt_values;

                SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
                FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


                There are no LOB pages in the index:



                ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
                ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
                ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
                ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2540 ║ 2540 ║
                ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2540 ║
                ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
                ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


                But if I add rows with values that take 8001 bytes:



                INSERT INTO #LOB_FOR_ME
                SELECT 2, REPLICATE(CAST('Z' AS VARCHAR(MAX)), 8001)
                FROM master..spt_values;

                SELECT index_level, index_type_desc, alloc_unit_type_desc, page_count, record_count
                FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('#LOB_FOR_ME'), 2, NULL , 'DETAILED');


                Now I have 1 LOB page in the index for every row that I just inserted:



                ╔═════════════╦════════════════════╦══════════════════════╦════════════╦══════════════╗
                ║ index_level ║ index_type_desc ║ alloc_unit_type_desc ║ page_count ║ record_count ║
                ╠═════════════╬════════════════════╬══════════════════════╬════════════╬══════════════╣
                ║ 0 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 2556 ║ 5080 ║
                ║ 1 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 18 ║ 2556 ║
                ║ 2 ║ NONCLUSTERED INDEX ║ IN_ROW_DATA ║ 1 ║ 18 ║
                ║ 0 ║ NONCLUSTERED INDEX ║ LOB_DATA ║ 2540 ║ 2540 ║
                ╚═════════════╩════════════════════╩══════════════════════╩════════════╩══════════════╝


                You can also see this with SET STATISTICS IO ON; and the right query. Consider the following query that only looks at rows with 8000 bytes:



                SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
                FROM #LOB_FOR_ME
                WHERE ID = 1;


                Results upon executing:




                Scan count 1, logical reads 2560, physical reads 0, read-ahead reads
                0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.




                If I instead query the rows with 8001 bytes:



                SELECT SUM(LEN(MAX_VERNON_WAS_HERE))
                FROM #LOB_FOR_ME
                WHERE ID = 2;


                Now I see lob reads:




                Scan count 1, logical reads 20, physical reads 0, read-ahead reads 0,
                lob logical reads 5080, lob physical reads 0, lob read-ahead reads 0.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 1 hour ago









                Joe ObbishJoe Obbish

                22k43392




                22k43392



























                    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%2f235102%2fif-a-varcharmax-column-is-included-in-an-index-is-the-entire-value-always-sto%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

                    Magento 2 duplicate PHPSESSID cookie when using session_start() in custom php scriptMagento 2: User cant logged in into to account page, no error showing!Magento duplicate on subdomainGrabbing storeview from cookie (after using language selector)How do I run php custom script on magento2Magento 2: Include PHP script in headerSession lock after using Cm_RedisSessionscript php to update stockMagento set cookie popupMagento 2 session id cookie - where to find it?How to import Configurable product from csv with custom attributes using php scriptMagento 2 run custom PHP script

                    Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

                    How to solve knockout JS error in Magento 2 Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2