Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit dd58d19

Browse files
committed
Resolving UUF items
1 parent 2b012a2 commit dd58d19

6 files changed

Lines changed: 11 additions & 3 deletions

File tree

azure-sql/database/maintenance-window-configure.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -228,6 +228,9 @@ The following steps set the maintenance window on an existing database or elasti
228228

229229
:::image type="content" source="media/maintenance-window-configure/maintenance.png" alt-text="Screenshot from the Azure portal of the SQL database Maintenance page." lightbox="media/maintenance-window-configure/maintenance.png":::
230230

231+
> [!NOTE]
232+
> The **Maintainance** page is only available for databases and elastic pools that support maintenance window configuration. If the page is not available, the database or pool does not support maintenance window configuration.
233+
231234
# [PowerShell](#tab/azure-powershell)
232235

233236
#### Set the maintenance window for an existing database
-5.17 KB
Loading

azure-sql/virtual-machines/windows/security-considerations-best-practices.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,9 @@ Azure Virtual Machine extensions are trusted Microsoft or 3rd party extensions t
199199

200200
## FIPS compliance
201201

202-
[FIPS](/azure/compliance/offerings/offering-fips-140-2) is a US government standard that defines minimum security requirements for cryptographic modules in information technology products and systems. SQL Server is capable of being FIPS compliant in [SQL Server 2016 and later](/troubleshoot/sql/database-engine/security/sql-2016-fips-140-2-compliant-mode) or [SQL Server 2014](/troubleshoot/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode) with [Extended Security Updates](/sql/sql-server/end-of-support/sql-server-extended-security-updates).
202+
[FIPS](/azure/compliance/offerings/offering-fips-140-2) is a US government standard that defines minimum security requirements for cryptographic modules in information technology products and systems. Some US government compliance programs such as FedRAMP or the Department of Defense Security Requirement Guide require the use of FIPS validated encryption.
203+
204+
SQL Server is capable of being FIPS compliant in [SQL Server 2016 and later](/troubleshoot/sql/database-engine/security/sql-2016-fips-140-2-compliant-mode) or [SQL Server 2014](/troubleshoot/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode) with [Extended Security Updates](/sql/sql-server/end-of-support/sql-server-extended-security-updates).
203205

204206
To be FIPS compliant with SQL Server on Azure VMs, you should be on Windows Server 2022, which has FIPS enabled by default. Windows Server 2019 can also be FIPS compliant if FIPS is manually enabled using the policy specified in Security Technical Implementation Guide (STIG) finding V-93511.
205207

docs/database-engine/availability-groups/windows/availability-group-is-not-ready-for-automatic-failover.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,12 +28,12 @@ helpviewer_keywords:
2828
The policy is in a healthy state when at least one secondary replica is automatic failover ready.
2929

3030
## Possible Causes
31-
The availability group is not ready for automatic failover. The primary replica is configured for automatic failover; however, the secondary replica is not ready for automatic failover. The secondary replica that is configured for automatic failover might be unavailable or its data synchronization state is currently not SYNCHRONIZED.
31+
The availability group is not ready for [automatic failover](failover-and-failover-modes-always-on-availability-groups.md#AutomaticFailover). The primary replica is configured for automatic failover; however, the secondary replica is not ready for automatic failover. The secondary replica that is configured for automatic failover might be unavailable or its [data synchronization state is currently not SYNCHRONIZED](data-synchronization-state-of-some-availability-database-is-not-healthy.md).
3232

3333
## Possible Solutions
3434
Following are possible solutions for this issue:
3535

36-
- Verify that at least one secondary replica is configured as automatic failover. If there is not a secondary replica configured as automatic failover, update the configuration of a secondary replica to be the automatic failover target with synchronous commit.
36+
- Verify that at least one secondary replica is configured as [automatic failover](failover-and-failover-modes-always-on-availability-groups.md#EnableAutoFo). If there is not a secondary replica configured as automatic failover, update the configuration of a secondary replica to be the automatic failover target with synchronous commit.
3737

3838
- Use the policy to verify that the data is in a synchronization state and the automatic failover target is SYNCHRONIZED, and then resolve the issue at the availability replica.
3939

docs/database-engine/configure-windows/scm-services-change-the-password-of-the-accounts-used.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ To change [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Authenticat
3131

3232
SQL Server Configuration Manager is the tool designed and authorized to change the settings of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] services. Changing a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] service by using the Windows Service Control Manager (**services.msc**) application doesn't always change all of the necessary settings and might prevent the service from functioning properly. However, in a clustered environment, after changing the password on the active node by using SQL Server Configuration Manager, you must change the password on the passive node by using the Service Control Manager.
3333

34+
It's also possible to automate password management through [group-managed service accounts](configure-windows-service-accounts-and-permissions.md#GMSA).
35+
3436
## Permissions
3537

3638
You must be an administrator of the computer to change the password used by a service.

docs/relational-databases/system-functions/sys-fn-hadr-is-primary-replica-transact-sql.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ sys.fn_hadr_is_primary_replica ( 'dbname' )
3737

3838
## Returns
3939
Returns data type **bit**: 1 if the database on the current instance is the primary replica, otherwise 0.
40+
Returns `NULL` if the database doesn't exist, or isn't part of an availability group.
4041

4142
## Remarks
4243
Use this function to conveniently determine whether the local instance is hosting the primary replica of the specified availability database. Sample code could be similar to the following.

0 commit comments

Comments
 (0)