Stale PITR SQL restore point

Matthew Brown 0 Reputation points
2026-10-05T13:54:17.9233333+00:00

Under Azure SQL Server\Data Management\Backups (Available Backups tab)

My SQL server has 2 databases. One database has a very stale date "Earliest PITR restore point" of August 31, 2026 and the other is within 6 days old. I ran the Diagnose and solve problems and all it detected was the SA password was too short. I updated the SA password to 15 characters with lots of complexity. I waited 2 days and still PITR date is still at 8/31. Anyone know how I can find the next problem as Diagnose finds no other issues?

Azure SQL Database
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 137.9K Reputation points MVP Volunteer Moderator
    2026-10-05T14:23:02.7833333+00:00

    My databases also has the earliest PITR restore point by the end of August. And it makes sense. If memory serves, the default for PITR backups is to keep them for 35 days. Keep in mind that this is the earliest, so if you would need to restore the database per, say, Sept 17th, that should be possible.

    If the database where the oldest possible PITR is only six days back, that's more puzzling if this database is as old as the other one. But maybe this is a newer database? Or it was actually restored six days ago.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.