Skip to content

Commit a3979d2

Browse files
authored
Update database-copy.md
Removed note about BSR being in preview.
1 parent 8de9a96 commit a3979d2

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/azure-sql/database/database-copy.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,6 @@ Azure SQL Database provides several methods for creating a copy of an existing [
2222

2323
A database copy is a transactionally consistent snapshot of the source database as of a point in time after the copy request is initiated. You can select the same server or a different server for the copy. Also you can choose to keep the backup redundancy, service tier and compute size of the source database, or use a different backup storage redundancy and/or compute size within the same or a different service tier. After the copy is complete, it becomes a fully functional, independent database. The logins, users, and permissions in the copied database are managed independently from the source database. The copy is created using the geo-replication technology. Once replica seeding is complete, the geo-replication link is automatically terminated. All the requirements for using geo-replication apply to the database copy operation. See [Active geo-replication overview](active-geo-replication-overview.md) for details.
2424

25-
> [!NOTE]
26-
> Azure SQL Database Configurable Backup Storage Redundancy is currently available in public preview in Brazil South and generally available in Southeast Asia Azure region only. In the preview, if the source database is created with locally-redundant or zone-redundant backup storage redundancy, database copy to a server in a different Azure region is not supported.
27-
2825
## Database Copy for Azure SQL Hyperscale
2926

3027
For Azure SQL Hyperscale the target database determines whether the copy will be a fast copy or a size of data copy.

0 commit comments

Comments
 (0)