Skip to content

Commit 20537b1

Browse files
committed
added note about scaling (AzB 1648251)
1 parent b8cb853 commit 20537b1

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/sql-database/sql-database-single-database-scale.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,10 @@ You are billed for each hour a database exists using the highest service tier +
120120
> [!IMPORTANT]
121121
> Under some circumstances, you may need to shrink a database to reclaim unused space. For more information, see [Manage file space in Azure SQL Database](sql-database-file-space-management.md).
122122
123+
### Geo-replicated database
124+
125+
To change the database size of a replicated secondary database, change the size of the primary database. This change will then be replicated and implemented on the secondary database as well.
126+
123127
## P11 and P15 constraints when max size greater than 1 TB
124128

125129
More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. The following considerations and limitations apply to P11 and P15 databases with a maximum size greater than 1 TB:

0 commit comments

Comments
 (0)