Backup Logs in Azure SQL Database

Question

Post reply

Backup Logs in Azure SQL Database

Michael L John

One Orange Chip

Points: 27060
More actions
September 2, 2022 at 4:08 pm

#4083376

We have multiple Azure SQL databases. Not managed instances or Azure VM's.
For our ISO auditing requirements, this is the requirement:
Backup configurations for databases holding critical information, including the notification settings and an example backup alert.
Providing the configuration is easy. What is not so easy is the "notification settings and an example backup alert" I tried to configure log analytics and the query I execute gives me no results.
There seems to be a lot of discrepancies in the documentation. Some things apply only to managed instances, yet it allows you to create these things against an Azure SQL database.
This is one of the default queries provided:
// Distribution of Backup Jobs by Status
// View the number of completed and failed Backup Jobs in the selected time range.
AddonAzureBackupJobs
//Get all Backup Jobs
| where JobOperation == "Backup"
//Remove duplicate records if any
| summarize arg_max(TimeGenerated, *) by JobUniqueId
//Summarize by Job Status
| summarize count(JobUniqueId) by JobStatus
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
September 6, 2022 at 6:46 am

This was removed by the editor as SPAM

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80325 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Jeff Moden SSC Guru Points: 1004409 More actions · Answer 2

I don't know if it helps or not, but that looks like it might be written in KQL. Don't ask me how to use it because I don't use Azure at all. It IS supposed to be "the bomb" for such things on Azure, though.

--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)