You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-domain-services/use-azure-monitor-workbooks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ To access the workbook template for the security overview report, complete the f
54
54
1. Select your managed domain, such as *aaddscontoso.com*
55
55
1. From the menu on the left-hand side, choose **Monitoring > Workbooks**
56
56
57
-

57
+

58
58
59
59
1. Choose the **Security Overview Report**.
60
60
1. From the drop-down menus at the top of the workbook, select your Azure subscription and then an Azure Monitor workspace.
Copy file name to clipboardExpand all lines: articles/advisor/advisor-high-availability-recommendations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ Azure Advisor checks for any VPN gateways that use a Basic SKU and recommends th
56
56
- Higher stability and availability.
57
57
58
58
## Ensure reliable outbound connectivity with VNet NAT
59
-
Using default outbound connecitivty provided by a Standard Load Balancer or other Azure resources is not recommended for production workloads as this causes connection failures (also called SNAT port exhaustion). The recommended approach is using a VNet NAT which will prevent any failures of connectivty in this regard. NAT can scale seamlessly to ensure your application is never out ports. [Learn more about VNet NAT](../virtual-network/nat-gateway/nat-overview.md).
59
+
Using default outbound connecitivty provided by a Standard Load Balancer or other Azure resources is not recommended for production workloads as this causes connection failures (also called SNAT port exhaustion). The recommended approach is using a VNet NAT which will prevent any failures of connectivity in this regard. NAT can scale seamlessly to ensure your application is never out ports. [Learn more about VNet NAT](../virtual-network/nat-gateway/nat-overview.md).
Copy file name to clipboardExpand all lines: articles/advisor/advisor-reference-performance-recommendations.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -281,7 +281,7 @@ Learn more about [MariaDB server - OrcasMariaDbStorageLimit (Scale the storage l
281
281
282
282
Our internal telemetry shows that the CPU has been running under high utilization for an extended period of time over the last 7 days. High CPU utilization may lead to slow query performance. To improve performance, we recommend moving to a larger compute size.
283
283
284
-
Learn more about [MariaDB server - OrcasMariaDbCpuOverlaod (Increase the MariaDB server vCores)](https://aka.ms/mariadbpricing).
284
+
Learn more about [MariaDB server - OrcasMariaDbCpuOverload (Increase the MariaDB server vCores)](https://aka.ms/mariadbpricing).
285
285
286
286
### Scale the MariaDB server to higher SKU
287
287
@@ -923,7 +923,7 @@ Learn more about [Database Instance - DisableIPv6Protocol (For improved file sys
923
923
924
924
The parameter net.ipv4.tcp_slow_start_after_idle disables the need to scale-up incrementally the TCP window size for TCP connections which were idle for some time. By setting this parameter to zero as per SAP note: 302436, the maximum speed is used from beginning for previously idle TCP connections
925
925
926
-
Learn more about [Database Instance - ParamterSlowStart (To improve file system performance in HANA DB with ANF, disable parameter for slow start after idle)](https://launchpad.support.sap.com/#/notes/3024346).
926
+
Learn more about [Database Instance - ParameterSlowStart (To improve file system performance in HANA DB with ANF, disable parameter for slow start after idle)](https://launchpad.support.sap.com/#/notes/3024346).
927
927
928
928
### For improved file system performance in HANA DB with ANF optimize tcp_max_syn_backlog OS parameter
929
929
@@ -937,11 +937,11 @@ Enable the tcp_sack parameter as per SAP note: 302436. This configuration certif
937
937
938
938
Learn more about [Database Instance - TCPSackParameter (For improved file system performance in HANA DB with ANF, enable the tcp_sack OS parameter)](https://launchpad.support.sap.com/#/notes/3024346).
939
939
940
-
### In high-availaility scenario for HANA DB with ANF, disable the tcp_timestamps OS parameter
940
+
### In high-availability scenario for HANA DB with ANF, disable the tcp_timestamps OS parameter
941
941
942
942
Disable the tcp_timestamps parameter as per SAP note: 302436. This configuration certifies HANA DB to run with ANF and improves file system performance in high-availability scenarios for HANA DB with ANF in SAP workloads
943
943
944
-
Learn more about [Database Instance - DisableTCPTimestamps (In high-availaility scenario for HANA DB with ANF, disable the tcp_timestamps OS parameter)](https://launchpad.support.sap.com/#/notes/3024346).
944
+
Learn more about [Database Instance - DisableTCPTimestamps (In high-availability scenario for HANA DB with ANF, disable the tcp_timestamps OS parameter)](https://launchpad.support.sap.com/#/notes/3024346).
945
945
946
946
### For improved file system performance in HANA DB with ANF, enable the tcp_timestamps OS parameter
0 commit comments