snapshot_previous_MonDmOsExceptionStats error on IndexOptimize

[JohnMTrollope]

I am on this version:

Microsoft SQL Azure (RTM) - 12.0.2000.8
Mar 23 2023 05:33:04
Copyright (C) 2022 Microsoft Corporation

I am running these parameters

EXECUTE dbo.IndexOptimize 
	@Databases = 'master',
	@MaxDOP = 1,
	@FragmentationLow = NULL,
	@FragmentationMedium = 'INDEX_REBUILD_ONLINE,INDEX_REORGANIZE',
	@FragmentationHigh = NULL,
	@FragmentationLevel1 = 1,
	@FragmentationLevel2 = 5,
	@MinNumberOfPages = 8192,
	@MaxNumberOfPages = 131072,
	@UpdateStatistics = 'ALL',
	@OnlyModifiedStatistics = 'Y',
	@MSShippedObjects = 'Y',
	@LogToTable = 'Y'

Eventually, the IndexOptimise runs this code (I have put in the parameters)

EXECUTE sp_executesql @stmt = @CurrentCommand, @params = N'@ParamDatabaseName nvarchar(max), @ParamObjectID int, @ParamIndexID int, @ParamPartitionNumber int, @ParamFragmentationLevel float OUTPUT, @ParamPageCount bigint OUTPUT', @ParamDatabaseName = @CurrentDatabaseName, @ParamObjectID = @CurrentObjectID, @ParamIndexID = @CurrentIndexID, @ParamPartitionNumber = @CurrentPartitionNumber, @ParamFragmentationLevel = @CurrentFragmentationLevel OUTPUT, @ParamPageCount = @CurrentPageCount OUTPUT

Which boils down to this:

SELECT MAX(avg_fragmentation_in_percent), SUM(page_count) FROM 
sys.dm_db_index_physical_stats(DB_ID('master'), 1271675578, 1, 1, 'LIMITED') 
WHERE alloc_unit_type_desc = 'IN_ROW_DATA' AND index_level = 0

I consistently get this and simply cannot find the object or anything about it on Google.

Msg 2591, Level 16, State 40, Line 11
Cannot find a row in the system catalog with the index ID 1 for table "snapshot_previous_MonDmOsExceptionStats".

The best I can do for now is to change Hallengren's code to skip it but really not keen to do that. Does anyone know what's going on?

Thanks
John

[JohnMTrollope]

Note: even when I run "@MSShippedObjects = 'N'", I get the same error.

[JohnMTrollope]

Ahh, the plot thickens for me as this works perfectly well on SQL 2019 and also SQL 2022 on prem.

use master; select object_name(1271675578) 

Which returns dbo.logon_audit - a table I use for auditing and is on all my 2019, 2022 and Azure environments.

That explains why @MSShippedObjects makes no difference. But it does seem to be uniquely an Azure managed instance issue

[JohnMTrollope]

The table in master does not cause an issue but the clustered index does. If I remove this, then there is no error

CREATE UNIQUE CLUSTERED INDEX pkLoginAudit ON dbo.LogonAudit (
	pk ASC
) WITH (
    PAD_INDEX = OFF, 
    STATISTICS_NORECOMPUTE = OFF, 
    SORT_IN_TEMPDB = OFF, 
    IGNORE_DUP_KEY = OFF, 
    DROP_EXISTING = OFF, 
    ONLINE = OFF, 
    ALLOW_ROW_LOCKS = ON, 
    ALLOW_PAGE_LOCKS = ON, 
    OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF
) ON [PRIMARY]

Alas this index is very necessary so I will just have Hallengren code ignore this table for now.