Skip to content

Commit 8f7bbf3

Browse files
committed
Broken link has removed
1 parent cce6d6e commit 8f7bbf3

1 file changed

Lines changed: 3 additions & 5 deletions

File tree

memdocs/configmgr/core/understand/site-size-performance-faq.yml

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,6 @@ sections:
9595
9696
- [Optimize application performance](/azure/storage/storage-premium-storage-performance#optimize-application-performance)
9797
98-
- [Disks guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance)
99-
10098
**Example: Azure-based site server**
10199
102100
[Sizing guidelines](../plan-design/configs/site-size-performance-guidelines.md#general-sizing-guidelines) for a colocated site server and SQL Server with **50,000** clients are eight cores, 32 GB, and 1200 IOPS for site server inboxes, and 2800 IOPS for SQL Server files.
@@ -110,7 +108,7 @@ sections:
110108
| 1xP30 (1024 GB) | 64k ReFS | SQL Server (all files<sup>2</sup>) | 2800 | 3112 |
111109
112110
1. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations).
113-
2. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
111+
2. Azure guidance allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
114112
115113
**Example: Azure-based site server (for instant performance increase)**
116114
@@ -128,7 +126,7 @@ sections:
128126
129127
1. Disks are striped using Storage Spaces.
130128
2. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations). VM size limits performance.
131-
3. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
129+
3. Azure guidance allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
132130
133131
If you need more performance in future, you can upsize your VM to a DS14v2, which will double CPU and memory. The additional disk bandwidth allowed by that VM size will also instantly boost the available disk IOPS on your previously configured disks.
134132
@@ -142,7 +140,7 @@ sections:
142140
143141
1. Disks are striped using Storage Spaces.
144142
2. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations). VM size limits performance.
145-
3. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
143+
3. Azure guidance allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
146144
147145
- name: Other common SQL Server-related performance questions
148146
questions:

0 commit comments

Comments
 (0)