January 7, 2019 at 5:17 am
I'm hoping someone can answer this for me. I have some tables that are fairly wide and long. The other day I did a restore down to Dev, did some index rebuilds and table truncations on them and then did a shrink. Suddenly DbccLOBCompact shows up in my sp_who2 results. I looked it up and Microsoft documentation list all sorts of datatypes that are not in my table. I have char, varchar(not max), money, int (tiny and regular), and smalldatetime datatypes.
Why in heavens name would SQL Server need to use a LOB shrink on these tables if I don't have text or varbinary or varchar(max), etc. on these tables? I would appreciate any thoughts on this issue.
January 7, 2019 at 12:27 pm
Here is a nice write up: https://sqlity.net/en/1051/blob-and-row-overflow-storage-internals-row-overflow-data/
Even if you don't have LOB data - if you exceed the maximum size of a page the data can be moved to row-overflow data pages and those pages are LOB type pages.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 7, 2019 at 12:39 pm
Jeffrey Williams 3188 - Monday, January 7, 2019 12:27 PMHere is a nice write up: https://sqlity.net/en/1051/blob-and-row-overflow-storage-internals-row-overflow-data/Even if you don't have LOB data - if you exceed the maximum size of a page the data can be moved to row-overflow data pages and those pages are LOB type pages.
Thank you, Jeff. That's probably what happened.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply