CHECKDB on Azure SQL DB?
This is a selfish post because I’ll probably forget and go googling for info on this topic, so I though I would link to an authoritative answer on the question, do you need to run DBCC CHECKDB on Azure SQL DB?
https://azure.microsoft.com/en-gb/blog/data-integrity-in-azure-sql-database/
Microsoft distinguished engineer Peter Carlin says you don’t need to, it is monitored by Azure on your behalf. And if something was to go wrong, they will also work with you to put things right.
Although Peter says you can run them if you want, his post gives me enough peace of mind to stop running these on my Azure SQL DB instances. Let me know if you agree in the comments.
For more Azure content, check out my Azure tag.
Is this still current advice now, in mid 2022?
I’d think Azure’s internal integrity checks would only become better since the original advice 5 years ago.
Surely ‘even better’ would mean this opinion rings true even more than ever. But bear in mind it is an opinion of mine and you should make up your own mind, based on your own research.
This does not appear to be the case with Managed Instance, where MS suggests scheduling CHECKDB around workload.
https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/automated-backups-overview?view=azuresql#backup-integrity
Yes, it does say that in MS Learn. So MI might need it, you should run it if you are unsure if you are covered.
Pretty sure that sentence is for running dbcc against a test restore of the database, not for the active MI database. MI backups, at the time, didn’t have the same test restores and checks non-MI backups do.