Lets you wind block blobs in a general-purpose v2 account back to how they were at an earlier moment. Before it works, soft delete, blob versioning and the change feed all have to be on.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Point-in-time restore in context, with comparison tables and the common traps.
Terms in this definition
- EARLIER
Within nested DAX row contexts, lets an inner calculation read a column as it stood in an outer pass; EARLIEST jumps to the outermost. Most people now use variables, which read more clearly.
- Soft delete
Retains deleted backups or data so they can be recovered during a retention period.
- BLOB
Short for binary large object: raw binary data, like pictures, audio, video or documents, that only an application can make sense of. Azure keeps these files as blobs in Blob Storage.
- Versioning
When enabled on Blob Storage, earlier versions of each blob are retained. Point-in-time restore depends on it, though it never purges data itself.
- Change feed
A log, in order, of changes made to blobs; point-in-time restore for block blobs depends on it.
- ALL
A DAX function that ignores any filters and gives back every row of a table or every value of the named columns. Used within CALCULATE, it works as a modifier that clears filters, although REMOVEFILTERS states that intent more clearly where it is available.
Related terms
- Automatic backups
Backups that Azure SQL takes on its own, allowing point-in-time restore over a window of 1 to 35 days. Keeping backups longer requires long-term retention (LTR).