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/azure-sql-iaas-vs-paas-what-is-overview.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
@@ -161,7 +161,7 @@ For **SQL on Azure VM**, Microsoft provides an availability SLA of 99.95% that c
161
161
162
162
**Azure SQL Managed Instance** greatly simplifies the migration of existing applications to Azure, enabling you to bring migrated database applications to market in Azure quickly.
163
163
164
-
**SQL on Azure VM** is perfect if your existing or new applications require large databases or access to all features in SQL Server or Windows/Linux, and you want to avoid the time and expense of acquiring new on-premises hardware. It is also a good fit when you want to migrate existing on-premises applications and databases to Azure as-is - in cases where SQL Database or SQL Managed Instance is not a good fit. Since you do not need to change the presentation, application, and data layers, you save time and budget on re-architecting your existing solution. Instead, you can focus on migrating all your solutions to Azure and in doing some performance optimizations that may be required by the Azure platform. For more information, see [Performance Best Practices for SQL Server on Azure Virtual Machines](./zirtual-zachines/windows/performance-guidelines-best-practices-checklist.md).
164
+
**SQL on Azure VM** is perfect if your existing or new applications require large databases or access to all features in SQL Server or Windows/Linux, and you want to avoid the time and expense of acquiring new on-premises hardware. It is also a good fit when you want to migrate existing on-premises applications and databases to Azure as-is - in cases where SQL Database or SQL Managed Instance is not a good fit. Since you do not need to change the presentation, application, and data layers, you save time and budget on re-architecting your existing solution. Instead, you can focus on migrating all your solutions to Azure and in doing some performance optimizations that may be required by the Azure platform. For more information, see [Performance Best Practices for SQL Server on Azure Virtual Machines](./virtual-machines/windows/performance-guidelines-best-practices-checklist.md).
Copy file name to clipboardExpand all lines: azure-sql/database/connect-query-content-reference-guide.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
@@ -46,7 +46,7 @@ Get the connection information you need to connect to the database in Azure SQL
46
46
3. On the **Overview** page, review the fully qualified server name next to **Server name** for the database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
47
47
48
48
> [!NOTE]
49
-
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
49
+
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
50
50
51
51
## Get ADO.NET connection information (optional - SQL Database only)
|**Configure**|[Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)|[Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
34
-
| **Configure** ||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md)
34
+
| **Configure** ||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
35
35
|**Load data**|Adventure Works loaded per quickstart|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|
36
36
|**Load data**||Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
37
37
@@ -55,7 +55,7 @@ Get the connection information you need to connect to the database. You'll need
55
55
3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
56
56
57
57
> [!NOTE]
58
-
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
58
+
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
| Configure |[Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)|[Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
33
-
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md)
33
+
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
34
34
|Load data|Adventure Works loaded per quickstart|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|
35
35
|||Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
36
36
@@ -73,7 +73,7 @@ Get the connection information you need to connect to the database in Azure SQL
73
73
3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
74
74
75
75
> [!NOTE]
76
-
> For connection information for SQL Server on Azure VM, see [Connect to SQL Server](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
76
+
> For connection information for SQL Server on Azure VM, see [Connect to SQL Server](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
| Configure |[Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)|[Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
34
-
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md)
34
+
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
35
35
|Load data|Adventure Works loaded per quickstart|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|
36
36
|||Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
37
37
@@ -61,7 +61,7 @@ Get the connection information you need to connect to the database in Azure SQL
61
61
3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server in an Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
62
62
63
63
> [!NOTE]
64
-
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
64
+
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
| Configure |[Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)|[Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
33
-
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md)
33
+
|||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
34
34
|Load data|Adventure Works loaded per quickstart|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|
35
35
|||Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
36
36
@@ -56,7 +56,7 @@ Get the connection information you need to connect to a database in Azure SQL Da
56
56
3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
57
57
58
58
> [!NOTE]
59
-
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
59
+
> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
60
60
61
61
## Create code to query your database in Azure SQL Database
| Configure |[Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)|[Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
36
-
|||[Connectivity from on-site](../managed-instance/point-to-site-p2s-configure.md) | [Connect to SQL Server](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md)
36
+
|||[Connectivity from on-site](../managed-instance/point-to-site-p2s-configure.md) | [Connect to SQL Server](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
37
37
|Load data|Adventure Works loaded per quickstart|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|[Restore Wide World Importers](../managed-instance/restore-sample-database-quickstart.md)|
38
38
|||Restore or import Adventure Works from [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
39
39
@@ -54,7 +54,7 @@ Get the connection information you need to connect to your database. You'll need
54
54
3. On the **Overview** page, review the fully qualified server name next to **Server name** for your database in SQL Database or the fully qualified server name (or IP address) next to **Host** for your managed instance in SQL Managed Instance or your SQL Server instance on your VM. To copy the server name or host name, hover over it and select the **Copy** icon.
55
55
56
56
> [!NOTE]
57
-
> For connection information for SQL Server on Azure VM, see [Connect to SQL Server](../zirtual-zachines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server)
57
+
> For connection information for SQL Server on Azure VM, see [Connect to SQL Server](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server)
0 commit comments