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: azure-sql/managed-instance/log-replay-service-migrate.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Migrate Databases by Using Log Replay Service
3
-
description: Learn how to migrate databases from a SQL Server to Azure SQL Managed Instance by using Log Replay Service.
2
+
title: Migrate SQL Server Databases by Using Log Replay Service
3
+
description: Migrate SQL Server databases to Azure SQL Managed Instance by using Log Replay Service (LRS). Step-by-step guide with prerequisites, best practices, and troubleshooting tips. Start your migration today.
This article explains how to migrate databases to Azure SQL Managed Instance by using [Log Replay Service (LRS)](log-replay-service-overview.md). LRS is a free-of-charge cloud service that's available for Azure SQL Managed Instance, based on SQL Server log-shipping technology.
24
+
This article explains how to migrate SQL Server databases to Azure SQL Managed Instance using [Log Replay Service (LRS)](log-replay-service-overview.md). LRS is a free cloud service for Azure SQL Managed Instance migrations, built on SQL Server log-shipping technology. Learn the complete process from prerequisites to cutover, including best practices for a successful database migration.
25
25
26
26
> [!NOTE]
27
27
> It's now possible to migrate your SQL Server instance enabled by Azure Arc to Azure SQL Managed Instance directly through the Azure portal. To learn more, review [Migrate to Azure SQL Managed Instance](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance).
Copy file name to clipboardExpand all lines: azure-sql/virtual-machines/windows/availability-group-manually-configure-tutorial-multi-subnet.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
@@ -102,7 +102,7 @@ During the prerequisites, you should have [assigned secondary IP addresses](avai
102
102
Assign these IP addresses as the cluster IP addresses for each relevant subnet.
103
103
104
104
> [!NOTE]
105
-
> On Windows Server 2019, the cluster creates a **Distributed Server Name** instead of the **Cluster Network Name**, and the cluster name object (CNO) is automatically registered with the IP addresses for all of the nodes in the cluster, eliminating the need for a dedicated windows cluster IP address. If you're on Windows Server 2019, either skip this section, and any other steps that refer to the **Cluster Core Resources** or create a virtual network name (VNN)-based cluster using [PowerShell](failover-cluster-instance-storage-spaces-direct-manually-configure.md#create-windows-failover-cluster). See the blog [Failover Cluster: Cluster Network Object](https://blogs.windows.com/windowsexperience/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/#W0YAxO8BfwBRbkzG.97) for more information.
105
+
> On Windows Server 2019 or later, the cluster creates a **Distributed Server Name** instead of the **Cluster Network Name**, and the cluster name object (CNO) is automatically registered with the IP addresses for all of the nodes in the cluster, eliminating the need for a dedicated windows cluster IP address. If you're on Windows Server 2019 or later, either skip this section, and any other steps that refer to the **Cluster Core Resources** or create a virtual network name (VNN)-based cluster using [PowerShell](failover-cluster-instance-storage-spaces-direct-manually-configure.md#create-windows-failover-cluster). See the blog [Failover Cluster: Cluster Network Object](https://blogs.windows.com/windowsexperience/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/#W0YAxO8BfwBRbkzG.97) for more information.
106
106
107
107
To change the cluster IP address, follow these steps:
This article provides a quick checklist as a series of best practices and guidelines to optimize performance of your SQL Server on Azure Virtual Machines (VMs).
17
+
This article provides checklists as part of a series of best practices and guidelines to optimize performance of your SQL Server on Azure Virtual Machines (VMs). Use this guide to improve your VM configuration, storage setup, security posture, and troubleshoot common performance issues.
18
18
19
-
For comprehensive details, see the other articles in this series: [VM size](performance-guidelines-best-practices-vm-size.md), [Storage](performance-guidelines-best-practices-storage.md), [Security](security-considerations-best-practices.md), [HADR configuration](hadr-cluster-best-practices.md), [Collect baseline](performance-guidelines-best-practices-collect-baseline.md).
19
+
The checklists in this article provide a brief overview of the more comprehensive details found in the following articles of this series:
Enable [SQL Assessment for SQL Server on Azure VMs](sql-assessment-for-sql-vm.md) and your SQL Server will be evaluated against known best practices with results on the [SQL VM management page](manage-sql-vm-portal.md) of the Azure portal.
22
28
@@ -35,11 +41,15 @@ For videos about the latest features to optimize SQL Server VM performance and a
35
41
36
42
While running SQL Server on Azure Virtual Machines, continue using the same database performance tuning options that are applicable to SQL Server in on-premises server environments. However, the performance of a relational database in a public cloud depends on many factors, such as the size of a virtual machine, and the configuration of the data disks.
37
43
38
-
There's typically a trade-off between optimizing for costs and optimizing for performance. This performance best practices series is focused on getting the *best* performance for SQL Server on Azure Virtual Machines. If your workload is less demanding, you might not require every recommended optimization. Consider your performance needs, costs, and workload patterns as you evaluate these recommendations.
44
+
There's typically a trade-off between optimizing for costs and optimizing for performance. This performance best practices series is focused on getting the *best* performance for SQL Server on Azure Virtual Machines.
45
+
46
+
**Next steps:** Start with the first [VM size recommendations](#vm-size) section, then proceed through [Storage](#storage), [Security](#security), and [SQL Server features](#sql-server-features) sections for a complete optimization approach.
47
+
48
+
If your workload is less demanding, you might not require every recommended optimization. Consider your performance needs, costs, and workload patterns as you evaluate these recommendations.
39
49
40
50
## Manually install SQL Server to an Azure VM
41
51
42
-
If you plan to manually install SQL Server on an Azure VM, consider the following:
52
+
If you plan to manually install SQL Server on an Azure VM, follow these essential steps to avoid common configuration issues:
43
53
44
54
- Make sure you have a product key ready for your installation.
45
55
- Avoid [unsupported](performance-guidelines-best-practices-vm-size.md#supportability) configurations such as:
@@ -124,7 +134,7 @@ The checklist in this section covers the [HADR best practices](hadr-cluster-best
124
134
125
135
## Performance troubleshooting
126
136
127
-
The following is a list of resources that help you further troubleshoot SQL Server performance issues.
137
+
When you encounter SQL Server performance issues, use these diagnostic resources to identify and resolve specific problems:
Consider enabling [SQL Assessment for SQL Server on Azure VMs](sql-assessment-for-sql-vm.md).
157
+
**Recommended tool:**[Enable SQL Assessment for SQL Server on Azure VMs](sql-assessment-for-sql-vm.md) to automatically evaluate your configuration against these best practices.
146
158
147
159
Review other SQL Server Virtual Machine articles at [SQL Server on Azure Virtual Machines Overview](sql-server-on-azure-vm-iaas-what-is-overview.md). If you have questions about SQL Server virtual machines, see the [Frequently Asked Questions](frequently-asked-questions-faq.yml).
This article provides storage best practices and guidelines to optimize performance for your SQL Server on Azure Virtual Machines (VM).
17
+
This article provides storage best practices and guidelines to optimize performance for your SQL Server on Azure Virtual Machines (VM). Learn how to select the right disk types, configure storage pools, and implement caching strategies to maximize your database performance.
18
18
19
19
There's typically a trade-off between optimizing for costs and optimizing for performance. This performance best practices series is focused on getting the *best* performance for SQL Server on Azure VMs. If your workload is less demanding, you might not require every recommended optimization. Consider your performance needs, costs, and workload patterns as you evaluate these recommendations.
Copy file name to clipboardExpand all lines: azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,8 @@ If you're new to SQL Server on Azure VMs, check out the *SQL Server on Azure VM
30
30
31
31
Azure virtual machines run in many different [geographic regions](https://azure.microsoft.com/regions/) around the world. They also offer various [machine sizes](/azure/virtual-machines/sizes). The virtual machine image gallery allows you to create a SQL Server VM with the right version, edition, and operating system. This makes virtual machines a good option for many different SQL Server workloads.
32
32
33
+
**Ready to get started?** Jump to our [quickstart guide](sql-vm-create-portal-quickstart.md) to create your first SQL Server VM, or explore the [feature benefits](#feature-benefits) you'll unlock by registering with the SQL IaaS Agent extension.
34
+
33
35
## Feature benefits
34
36
35
37
When you register your SQL Server on Azure VM with the [SQL IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md) you unlock a number of feature benefits. Registering with the extension is completely free.
@@ -42,7 +44,7 @@ The following table details the benefits unlocked by the extension:
42
44
43
45
To get started with SQL Server on Azure VMs, review the following resources:
44
46
45
-
-**Create SQL VM**: To create your SQL Server on Azure VM, review the Quickstarts using the [Azure portal](sql-vm-create-portal-quickstart.md), [Azure PowerShell](sql-vm-create-powershell-quickstart.md) or an [ARM template](create-sql-vm-resource-manager-template.md). For more thorough guidance, review the [Provisioning guide](create-sql-vm-portal.md).
47
+
-**Create your first SQL Server VM**: Get up and running quickly with our step-by-step quickstarts for the [Azure portal](sql-vm-create-portal-quickstart.md), [Azure PowerShell](sql-vm-create-powershell-quickstart.md), or [ARM template](create-sql-vm-resource-manager-template.md). For comprehensive setup guidance, see the complete [provisioning guide](create-sql-vm-portal.md).
46
48
-**Connect to SQL VM**: To connect to your SQL Server on Azure VMs, review the [ways to connect](ways-to-connect-to-sql.md).
47
49
-**Unlock feature benefits**: Registering your SQL Server VM with the [SQL IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md) unlocks a number of feature benefits, such as automated backup and patching.
48
50
-**Manage SQL VM from the portal**: You can manage SQL Server settings directly from the Azure portal by using the [SQL virtual machines](manage-sql-vm-portal.md) resource.
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/availability-database-is-suspended.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
@@ -33,7 +33,7 @@ helpviewer_keywords:
33
33
- The database administrator might have suspended data synchronization for maintenance purposes.
34
34
35
35
## Possible Solution
36
-
Resume data synchronization. If the issue persists, check the availability group in the Event log, and then diagnose why the system suspended data movement.
36
+
Resume data synchronization by right-clicking the availability group and selecting **Resume Data Movement**. If the issue persists, check the availability group in the Event log, and then diagnose why the system suspended data movement.
37
37
38
38
## See Also
39
39
[Overview of Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
0 commit comments