Skip to content

Commit 6f35fb8

Browse files
authored
Update PITR limitation to same server only
1 parent 39c1564 commit 6f35fb8

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-sql/database/recovery-using-backups.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,9 @@ When complete, the restore creates a new database on the same server as the orig
6464

6565
You generally restore a database to an earlier point for recovery purposes. You can treat the restored database as a replacement for the original database or use it as a data source to update the original database.
6666

67+
> [!IMPORTANT]
68+
> You can only run restore on the same server, cross-server restoration is not supported by Point-in-time restore.
69+
6770
- **Database replacement**
6871

6972
If you intend the restored database to be a replacement for the original database, you should specify the original database's compute size and service tier. You can then rename the original database and give the restored database the original name by using the [ALTER DATABASE](/sql/t-sql/statements/alter-database-azure-sql-database) command in T-SQL.

0 commit comments

Comments
 (0)