Index Fragmentation showing up blank
-
Hi All,
I'm checking indexes on a table and it seems to show up blank for all indexes in that database. It is the only affected database on the instance.
I currently running the version
Microsoft SQL Server 2012 (SP2-GDR) (KB3194719) - 11.0.5388.0 (X64)
(screenshot below shows a table that has millions of rows)
When I run the fragmentation report query it shows data.
-
This somewhat reminds me of a scenario I came across once where the database was really small, and the tables had been around for a LOT of years, and the server was small too, and they had just rebuilt the indexes, so the indexes were not at all fragmented, but the tables were all a god-awful mess because disk space for the database had always been extremely tight. I came in at the point that they were running out of space, in part because they had just rebuilt all the indexes, so I set the db to at least autogrow, after ensuring they had a much larger drive to operate on. This is eerily reminiscent...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy) - deep_trance_ - Thursday, May 17, 2018 7:48 PM
Hi All,
I'm checking indexes on a table and it seems to show up blank for all indexes in that database. It is the only affected database on the instance.
I currently running the version
Microsoft SQL Server 2012 (SP2-GDR) (KB3194719) - 11.0.5388.0 (X64)
(screenshot below shows a table that has millions of rows)When I run the fragmentation report query it shows data.
Maybe try executing DBCC UPDATEUSAGE for some of the indexes (or the table, depends on the size as it can be resource intensive) and see if that makes a difference.
DBCC UPDATEUSAGE (Transact-SQL)Sue
-
First step is to update both SQL Server 2012 to the latest SP/CU because there was still a lot of regressive code in SP2. They didn't get most of it fixed until SP3 CU6 (IIRC) and it's up to SP4 now.
Also, update SSMS.
If it persists, report it because it could be a rounding error to 100% and then only displaying the last two digits of the value.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) - Jeff Moden - Friday, May 18, 2018 1:34 PM
Thanks Jeff,
Updating to the latest SP/CU fixed the issue.
Danny
- deep_trance_ - Monday, May 21, 2018 6:26 PM
Excellent. Thank you for the feedback.
As a bit of a sidebar, SQL Server and SSMS has some extremely complex code behind the scenes but you do have to wonder how they let faults like this out.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply