Skip to content

Commit 9874c40

Browse files
committed
fixing things
1 parent 1d2dd9c commit 9874c40

File tree

9 files changed

+21
-21
lines changed

9 files changed

+21
-21
lines changed

articles/azure-sql/database/logical-servers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.date: 03/12/2019
1515
---
1616
# What is a logical SQL server in Azure SQL Database and Azure Synapse?
1717

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.
1919

2020
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.
2121

@@ -78,7 +78,7 @@ To manage an existing database, navigate to the **SQL databases** page and click
7878
> [!IMPORTANT]
7979
> 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.
8080
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).
8282

8383
| Cmdlet | Description |
8484
| --- | --- |
@@ -103,7 +103,7 @@ To create and manage servers, databases, and firewalls with Azure PowerShell, us
103103
104104
## Manage servers, databases, and firewalls using the Azure CLI
105105

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).
107107

108108
| Cmdlet | Description |
109109
| --- | --- |
@@ -133,7 +133,7 @@ To create and manage servers, databases, and firewalls with the [Azure CLI](/cli
133133
134134
## Manage servers, databases, and firewalls using Transact-SQL
135135

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).
137137

138138
> [!IMPORTANT]
139139
> You cannot create or delete a server using Transact-SQL.
172 KB
Loading

articles/azure-sql/database/network-access-controls-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -152,5 +152,5 @@ Private Link allows you to connect to a server via a **private endpoint**. A pri
152152
- For an overview of Azure SQL Database security, see [Securing your database](../../sql-database/sql-database-security-overview.md)
153153

154154
<!--Image references-->
155-
[1]: ./media/sql-database-get-started-portal/new-server2.png
156-
[2]: ./media/sql-database-get-started-portal/manage-server-firewall.png
155+
[1]: ../../sql-database/media/sql-database-get-started-portal/new-server2.png
156+
[2]: ../../sql-database/media/sql-database-get-started-portal/manage-server-firewall.png

articles/azure-sql/database/private-endpoint-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 03/09/2020
1313

1414
# Private Link for Azure SQL Database and Azure Synapse Analytics
1515

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.
1717

1818
> [!IMPORTANT]
1919
> 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
180180
- For an overview of Azure SQL Database connectivity, see [Azure SQL Connectivity Architecture](connectivity-architecture.md)
181181

182182
<!--Image references-->
183-
[1]: ./media/sql-database-get-started-portal/pe-connect-overview.png
184-
[2]: ./media/sql-database-get-started-portal/telnet-result.png
185-
[3]: ./media/sql-database-get-started-portal/pec-list-before.png
186-
[4]: ./media/sql-database-get-started-portal/pec-approve.png
187-
[5]: ./media/sql-database-get-started-portal/pec-list-after.png
188-
[6]: ./media/sql-database-get-started-portal/pec-select.png
183+
[1]: ../../sql-database/media/sql-database-get-started-portal/pe-connect-overview.png
184+
[2]: ../../sql-database/media/sql-database-get-started-portal/telnet-result.png
185+
[3]: ../../sql-database/media/sql-database-get-started-portal/pec-list-before.png
186+
[4]: ../../sql-database/media/sql-database-get-started-portal/pec-approve.png
187+
[5]: ../../sql-database/media/sql-database-get-started-portal/pec-list-after.png
188+
[6]: ../../sql-database/media/sql-database-get-started-portal/pec-select.png

articles/azure-sql/database/service-tier-hyperscale.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The Hyperscale service tier in Azure SQL Database is the newest service tier in
2525

2626
> [!NOTE]
2727
>
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).
2929
> - The hyperscale service tier is currently only available for Azure SQL Database, and not Azure SQL Managed Instance.
3030
3131
## What are the Hyperscale capabilities
@@ -221,7 +221,7 @@ These are the current limitations to the Hyperscale service tier as of GA. We a
221221
## Next steps
222222

223223
- 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)
225225
- 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.
226226
- 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).
227227
- For a features and comparison list, see [SQL common features](../../sql-database/sql-database-features.md).

articles/azure-sql/database/tutorial-secure-database.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,9 @@ Azure SQL Database secures data by allowing you to:
3030
- Enable security features
3131

3232
> [!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).
3434
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.
3636

3737
> [!TIP]
3838
> 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
5555

5656
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).
5757

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.
5959

6060
> [!NOTE]
6161
> 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:
136136
For information about configuring Azure AD, see:
137137

138138
- [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)
140140
- [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)
142142
- [Manage Azure AD using PowerShell](/powershell/azure/overview?view=azureadps-2.0)
143143
- [Hybrid identity required ports and protocols](../../active-directory/hybrid/reference-connect-ports.md)
144144

@@ -180,7 +180,7 @@ To add a user with SQL authentication:
180180

181181
### Azure AD authentication
182182

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.
184184

185185
> [!NOTE]
186186
> 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.
172 KB
Loading
116 KB
Loading
34 KB
Loading

0 commit comments

Comments
 (0)