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/azure-sql/database/logical-servers.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
@@ -15,7 +15,7 @@ ms.date: 03/12/2019
15
15
---
16
16
# What is a logical SQL server in Azure SQL Database and Azure Synapse?
17
17
18
-
In Azure SQL Database and Azure Synapse, a server is a logical construct that acts as a central administrative point for a collection of databases. At the server level, you can administer [logins](../../sql-database/sql-database-manage-logins.md), [firewall rules](firewall-configure.md), [auditing rules](../../sql-database/sql-database-auditing.md), [threat detection policies](../../sql-database/sql-database-threat-detection.md), and [failover groups](../../sql-database/sql-database-auto-failover-group.md). A server can be in a different region than its resource group. The server must exist before you can create a database in Azure SQL Database or a data warehouse database in Azure Synapse. All databases managed by a single server are created within the same region as the server.
18
+
In Azure SQL Database and Azure Synapse, a server is a logical construct that acts as a central administrative point for a collection of databases. At the server level, you can administer [logins](../../sql-database/sql-database-manage-logins.md), [firewall rules](firewall-configure.md), [auditing rules](../../sql-database/sql-database-auditing.md), [threat detection policies](../../sql-database/sql-database-threat-detection.md), and [auto-failover groups](../../sql-database/sql-database-auto-failover-group.md). A server can be in a different region than its resource group. The server must exist before you can create a database in Azure SQL Database or a data warehouse database in Azure Synapse. All databases managed by a single server are created within the same region as the server.
19
19
20
20
This server is distinct from a SQL Server instance that you may be familiar with in the on-premises world. Specifically, there are no guarantees regarding location of the databases or data warehouse database in relation to the server that manages them. Furthermore, neither Azure SQL Database nor Azure Synapse expose any instance-level access or features. In contrast, the instance databases in a managed instance are all physically co-located - in the same way that you are familiar with SQL Server in the on-premises or virtual machine world.
21
21
@@ -78,7 +78,7 @@ To manage an existing database, navigate to the **SQL databases** page and click
78
78
> [!IMPORTANT]
79
79
> The PowerShell Azure Resource Manager module is still supported, but all future development is for the Az.Sql module. For these cmdlets, see [AzureRM.Sql](https://docs.microsoft.com/powershell/module/AzureRM.Sql/). The arguments for the commands in the Az module and in the AzureRm modules are substantially identical.
80
80
81
-
To create and manage servers, databases, and firewalls with Azure PowerShell, use the following PowerShell cmdlets. If you need to install or upgrade PowerShell, see [Install Azure PowerShell module](/powershell/azure/install-az-ps). For creating and managing elastic pools, see [Elastic pools](../azure-sql/database/elastic-pool-overview.md).
81
+
To create and manage servers, databases, and firewalls with Azure PowerShell, use the following PowerShell cmdlets. If you need to install or upgrade PowerShell, see [Install Azure PowerShell module](/powershell/azure/install-az-ps). For creating and managing elastic pools, see [Elastic pools](elastic-pool-overview.md).
82
82
83
83
| Cmdlet | Description |
84
84
| --- | --- |
@@ -103,7 +103,7 @@ To create and manage servers, databases, and firewalls with Azure PowerShell, us
103
103
104
104
## Manage servers, databases, and firewalls using the Azure CLI
105
105
106
-
To create and manage servers, databases, and firewalls with the [Azure CLI](/cli/azure), use the following [Azure CLI SQL Database](/cli/azure/sql/db) commands. Use the [Cloud Shell](/azure/cloud-shell/overview) to run the CLI in your browser, or [install](/cli/azure/install-azure-cli) it on macOS, Linux, or Windows. For creating and managing elastic pools, see [Elastic pools](../azure-sql/database/elastic-pool-overview.md).
106
+
To create and manage servers, databases, and firewalls with the [Azure CLI](/cli/azure), use the following [Azure CLI SQL Database](/cli/azure/sql/db) commands. Use the [Cloud Shell](/azure/cloud-shell/overview) to run the CLI in your browser, or [install](/cli/azure/install-azure-cli) it on macOS, Linux, or Windows. For creating and managing elastic pools, see [Elastic pools](elastic-pool-overview.md).
107
107
108
108
| Cmdlet | Description |
109
109
| --- | --- |
@@ -133,7 +133,7 @@ To create and manage servers, databases, and firewalls with the [Azure CLI](/cli
133
133
134
134
## Manage servers, databases, and firewalls using Transact-SQL
135
135
136
-
To create and manage servers, databases, and firewalls with Transact-SQL, use the following T-SQL commands. You can issue these commands using the Azure portal, [SQL Server Management Studio](/sql/ssms/use-sql-server-management-studio), [Visual Studio Code](https://code.visualstudio.com/docs), or any other program that can connect to a server and pass Transact-SQL commands. For managing elastic pools, see [Elastic pools](../azure-sql/database/elastic-pool-overview.md).
136
+
To create and manage servers, databases, and firewalls with Transact-SQL, use the following T-SQL commands. You can issue these commands using the Azure portal, [SQL Server Management Studio](/sql/ssms/use-sql-server-management-studio), [Visual Studio Code](https://code.visualstudio.com/docs), or any other program that can connect to a server and pass Transact-SQL commands. For managing elastic pools, see [Elastic pools](elastic-pool-overview.md).
137
137
138
138
> [!IMPORTANT]
139
139
> You cannot create or delete a server using Transact-SQL.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/private-endpoint-overview.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.date: 03/09/2020
13
13
14
14
# Private Link for Azure SQL Database and Azure Synapse Analytics
15
15
16
-
Private Link allows you to connect to various PaaS services in Azure via a **private endpoint**. For a list of PaaS services that support Private Link functionality, go to the [Private Link Documentation](../private-link/index.yml) page. A private endpoint is a private IP address within a specific [VNet](../virtual-network/virtual-networks-overview.md) and subnet.
16
+
Private Link allows you to connect to various PaaS services in Azure via a **private endpoint**. For a list of PaaS services that support Private Link functionality, go to the [Private Link Documentation](../../private-link/index.yml) page. A private endpoint is a private IP address within a specific [VNet](../../virtual-network/virtual-networks-overview.md) and subnet.
17
17
18
18
> [!IMPORTANT]
19
19
> This article applies to both Azure SQL Database and Azure Synapse Analytics (formerly SQL Data Warehouse). For simplicity, the term 'database' refers to both databases in Azure SQL Database and Azure Synapse Analytics. Likewise, any references to 'server' is referring to the [logical SQL server](logical-servers.md) that hosts Azure SQL Database and Azure Synapse Analytics. This article does *not* apply to **Azure SQL Managed Instance**.
@@ -180,9 +180,9 @@ PolyBase is commonly used to load data into Azure Synapse Analytics from Azure S
180
180
- For an overview of Azure SQL Database connectivity, see [Azure SQL Connectivity Architecture](connectivity-architecture.md)
Copy file name to clipboardExpand all lines: articles/azure-sql/database/service-tier-hyperscale.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ The Hyperscale service tier in Azure SQL Database is the newest service tier in
25
25
26
26
> [!NOTE]
27
27
>
28
-
> - For details on the General Purpose and Business Critical service tiers in the vCore-based purchasing model, see [General Purpose](../../sql-database/sql-database-service-tier-general-purpose.md) and [Business Critical](../../sql-database/sql-database-service-tier-business-critical.md) service tiers. For a comparison of the vCore-based purchasing model with the DTU-based purchasing model, see [Azure SQL Database purchasing models and resources](sql-database-service-tiers.md).
28
+
> - For details on the General Purpose and Business Critical service tiers in the vCore-based purchasing model, see [General Purpose](../../sql-database/sql-database-service-tier-general-purpose.md) and [Business Critical](../../sql-database/sql-database-service-tier-business-critical.md) service tiers. For a comparison of the vCore-based purchasing model with the DTU-based purchasing model, see [Azure SQL Database purchasing models and resources](../../sql-database/sql-database-purchase-models.md).
29
29
> - The hyperscale service tier is currently only available for Azure SQL Database, and not Azure SQL Managed Instance.
30
30
31
31
## What are the Hyperscale capabilities
@@ -221,7 +221,7 @@ These are the current limitations to the Hyperscale service tier as of GA. We a
221
221
## Next steps
222
222
223
223
- For an FAQ on Hyperscale, see [Frequently asked questions about Hyperscale](../../sql-database/sql-database-service-tier-hyperscale-faq.md).
224
-
- For information about service tiers, see [Service tiers](sql-database-service-tiers.md)
224
+
- For information about service tiers, see [Service tiers](../../sql-database/sql-database-purchase-models.md)
225
225
- See [Overview of resource limits on a server](sql-database-resource-limits-logical-server.md) for information about limits at the server and subscription levels.
226
226
- For purchasing model limits for a single database, see [Azure SQL Database vCore-based purchasing model limits for a single database](../../sql-database/sql-database-vcore-resource-limits-single-databases.md).
227
227
- For a features and comparison list, see [SQL common features](../../sql-database/sql-database-features.md).
Copy file name to clipboardExpand all lines: articles/azure-sql/database/tutorial-secure-database.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,9 @@ Azure SQL Database secures data by allowing you to:
30
30
- Enable security features
31
31
32
32
> [!NOTE]
33
-
> Azure SQL Managed Instance is secured using network security rules and private endpoints as described in [Azure SQL Managed Instance](sql-database-managed-instance-index.yml) and [connectivity architecture](sql-database-managed-instance-connectivity-architecture.md).
33
+
> Azure SQL Managed Instance is secured using network security rules and private endpoints as described in [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance) and [connectivity architecture](../../sql-database/sql-database-managed-instance-connectivity-architecture.md).
34
34
35
-
To learn more, see the [Azure SQL Database security overview](/azure/sql-database/sql-database-security-index) and [capabilities](sql-database-security-overview.md) articles.
35
+
To learn more, see the [Azure SQL Database security overview](/azure/sql-database/sql-database-security-index) and [capabilities](../../sql-database/sql-database-security-overview.md) articles.
36
36
37
37
> [!TIP]
38
38
> The following Microsoft Learn module helps you learn for free about how to [Secure your Azure SQL Database](https://docs.microsoft.com/learn/modules/secure-your-azure-sql-database/).
@@ -55,7 +55,7 @@ For all steps in the tutorial, sign in to [Azure portal](https://portal.azure.co
55
55
56
56
SQL databases are protected by firewalls in Azure. By default, all connections to the server and database are rejected. To learn more, see [server-level and database-level firewall rules](firewall-configure.md).
57
57
58
-
Set **Allow access to Azure services** to **OFF** for the most secure configuration. Then, create a [reserved IP (classic deployment)](../virtual-network/virtual-networks-reserved-public-ip.md) for the resource that needs to connect, such as an Azure VM or cloud service, and only allow that IP address access through the firewall. If you're using the [resource manager](/azure/virtual-network/virtual-network-ip-addresses-overview-arm) deployment model, a dedicated public IP address is required for each resource.
58
+
Set **Allow access to Azure services** to **OFF** for the most secure configuration. Then, create a [reserved IP (classic deployment)](/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip) for the resource that needs to connect, such as an Azure VM or cloud service, and only allow that IP address access through the firewall. If you're using the [resource manager](/azure/virtual-network/virtual-network-ip-addresses-overview-arm) deployment model, a dedicated public IP address is required for each resource.
59
59
60
60
> [!NOTE]
61
61
> SQL Database communicates over port 1433. If you're trying to connect from within a corporate network, outbound traffic over port 1433 may not be allowed by your network's firewall. If so, you can't connect to the server unless your administrator opens port 1433.
@@ -136,9 +136,9 @@ To set the Azure AD administrator:
136
136
For information about configuring Azure AD, see:
137
137
138
138
- [Integrate your on-premises identities with Azure AD](../../active-directory/hybrid/whatis-hybrid-identity.md)
139
-
- [Add your own domain name to Azure AD](../active-directory/active-directory-domains-add-azure-portal.md)
139
+
- [Add your own domain name to Azure AD](../../active-directory/fundamentals/add-custom-domain.md)
140
140
- [Microsoft Azure now supports federation with Windows Server AD](https://azure.microsoft.com/blog/20../../windows-azure-now-supports-federation-with-windows-server-active-directory/)
141
-
- [Administer your Azure AD directory](../active-directory/fundamentals/active-directory-administer.md)
141
+
- [Administer your Azure AD directory](../../active-directory/fundamentals/active-directory-whatis.md)
142
142
- [Manage Azure AD using PowerShell](/powershell/azure/overview?view=azureadps-2.0)
143
143
- [Hybrid identity required ports and protocols](../../active-directory/hybrid/reference-connect-ports.md)
144
144
@@ -180,7 +180,7 @@ To add a user with SQL authentication:
180
180
181
181
### Azure AD authentication
182
182
183
-
Azure Active Directory authentication requires that database users are created as contained. A contained database user maps to an identity in the Azure AD directory associated with the database and has no login in the *master* database. The Azure AD identity can either be for an individual user or a group. For more information, see [Contained database users, make your database portable](https://msdn.microsoft.com/library/ff929188.aspx) and review the [Azure AD tutorial](./sql-database-aad-authentication-configure.md) on how to authenticate using Azure AD.
183
+
Azure Active Directory authentication requires that database users are created as contained. A contained database user maps to an identity in the Azure AD directory associated with the database and has no login in the *master* database. The Azure AD identity can either be for an individual user or a group. For more information, see [Contained database users, make your database portable](/sql/relational-databases/security/contained-database-users-making-your-database-portable) and review the [Azure AD tutorial](../../sql-database/sql-database-aad-authentication-configure.md) on how to authenticate using Azure AD.
184
184
185
185
> [!NOTE]
186
186
> Database users (excluding administrators) cannot be created using the Azure portal. Azure RBAC roles do not propagate to SQL servers, databases, or data warehouses. They are only used to manage Azure resources and do not apply to database permissions.
0 commit comments