- Login failed for user – Verify that the username and password are correct and that the firewall rules allow your client IP.
- Timeout expired – Check network latency, enable
Retry Logic, and consider scaling up the database tier.
- Azure AD authentication errors – Ensure the service principal has appropriate permissions and the token is valid.
- High CPU usage – Review missing indexes, long‑running queries, and use
Query Performance Insight.
- Slow query execution – Run
sys.dm_db_resource_stats and consider index tuning or scaling to a higher service tier.
- Blocking & deadlocks – Use
Extended Events or Deadlock Graph to identify conflict patterns.
4060 – Cannot open database. Verify that the database exists and the user has access.40197 – Service encountered an error. Retry after a short delay; if persists, contact support.10928/10929 – Resource limits reached. Consider scaling up or adjusting DTU/EU limits.
- Point‑in‑time restore unavailable – Ensure the database is in a service tier that supports PITR and retains backups.
- Long restore times – Verify that the target tier has sufficient I/O capacity; consider using Geo‑restore from a nearby region.
- Backup storage exhausted – Review long‑term retention policies and delete obsolete backups.