We used page-level compression on the table and its indexes, e.g., for compressing the table, we used the command alter table [msab_magento].[sales_order_item] rebuild partition = all with (data_compression = page);.

Ignoring the user is OK for me.

By the way, in my system under test, the Management Studio is in version 13.0.16106.4, and the SQL Server 14 is in version (SP2-GDR) (KB4505220) - 13.0.5101.9 (X64).

Tentatively, I believe the GUI Management Studio generates wrong SQLs for undoing compression on an index, e.g., it gets ALTER INDEX [SALES_ORDER_UPDATED_AT] ON [msab_magento].[sales_order] REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON). Noticed there is no DATA_COMPRESSION = NONE in the statement, and the index still shows row-level compressed after executing the command. Am I seeing the same symptoms as everyone else?