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/alerts-insights-configure-portal.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
@@ -19,7 +19,7 @@ ms.date: 05/04/2020
19
19
This article shows you how to set up alerts for databases in Azure SQL Database and Azure Synapse (formerly Azure SQL Data Warehouse) using the Azure portal. Alerts can send you an email or call a web hook when some metric (for example database size or CPU usage) reaches the threshold. This article also provides best practices for setting alert periods.
20
20
21
21
> [!NOTE]
22
-
> For SQL managed instance specific instructions, see [Create alerts for Azure SQL Managed Instance](../managed-instance/alerts-create.md).
22
+
> For Azure SQL Managed Instance specific instructions, see [Create alerts for Azure SQL Managed Instance](../managed-instance/alerts-create.md).
23
23
24
24
You can receive an alert based on monitoring metrics for, or events on, your Azure services.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-database-client-library.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
@@ -14,7 +14,7 @@ ms.date: 09/25/2018
14
14
---
15
15
# Building scalable cloud databases
16
16
17
-
Scaling out databases can be easily accomplished using scalable tools and features for Azure SQL Database. In particular, you can use the **Elastic Database client library** to create and manage scaled-out databases. This feature lets you easily develop sharded applications using hundreds—or even thousands—of Azure SQL databases.
17
+
Scaling out databases can be easily accomplished using scalable tools and features for Azure SQL Database. In particular, you can use the **Elastic Database client library** to create and manage scaled-out databases. This feature lets you easily develop sharded applications using hundreds—or even thousands—of databases in Azure SQL Database.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-pool-manage.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
@@ -62,7 +62,7 @@ To create and manage SQL Database elastic pools and pooled databases with Azure
62
62
To create and manage SQL Database elastic pools 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.
63
63
64
64
> [!TIP]
65
-
> For Azure CLI example scripts, see [Use CLI to move an Azure SQL database in a SQL elastic pool](scripts/move-database-between-elastic-pools-cli.md) and [Use Azure CLI to scale a SQL elastic pool in Azure SQL Database](scripts/scale-pool-cli.md).
65
+
> For Azure CLI example scripts, see [Use CLI to move a database in SQL Database in a SQL elastic pool](scripts/move-database-between-elastic-pools-cli.md) and [Use Azure CLI to scale a SQL elastic pool in Azure SQL Database](scripts/scale-pool-cli.md).
66
66
>
67
67
68
68
| Cmdlet | Description |
@@ -88,7 +88,7 @@ To create and move databases within existing elastic pools or to return informat
88
88
|[ALTER DATABASE (Azure SQL Database)](/sql/t-sql/statements/alter-database-azure-sql-database)|Move a database into, out of, or between elastic pools.|
89
89
|[DROP DATABASE (Transact-SQL)](/sql/t-sql/statements/drop-database-transact-sql)|Deletes a database.|
90
90
|[sys.elastic_pool_resource_stats (Azure SQL Database)](/sql/relational-databases/system-catalog-views/sys-elastic-pool-resource-stats-azure-sql-database)|Returns resource usage statistics for all the elastic pools on a server. For each elastic pool, there is one row for each 15 second reporting window (four rows per minute). This includes CPU, IO, Log, storage consumption and concurrent request/session utilization by all databases in the pool.|
91
-
|[sys.database_service_objectives (Azure SQL Database)](/sql/relational-databases/system-catalog-views/sys-database-service-objectives-azure-sql-database)|Returns the edition (service tier), service objective (pricing tier), and elastic pool name, if any, for an Azure SQL database or an Azure SQL Data Warehouse. If logged on to the master database in a server, returns information on all databases. For Azure SQL Data Warehouse, you must be connected to the master database.|
91
+
|[sys.database_service_objectives (Azure SQL Database)](/sql/relational-databases/system-catalog-views/sys-database-service-objectives-azure-sql-database)|Returns the edition (service tier), service objective (pricing tier), and elastic pool name, if any, for a database in SQL Database or Azure SQL Data Warehouse. If logged on to the master database in a server, returns information on all databases. For Azure SQL Data Warehouse, you must be connected to the master database.|
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-pool-overview.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
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Manage multiple databases with elastic pools
3
-
description: Manage and scale multiple SQL databases - hundreds and thousands - using elastic pools. One price for resources you can distribute where needed.
3
+
description: Manage and scale multiple databases in Azure SQL Database - hundreds and thousands - using elastic pools. One price for resources you can distribute where needed.
4
4
services: sql-database
5
5
ms.service: sql-database
6
6
ms.subservice: elastic-pools
@@ -12,7 +12,7 @@ ms.author: moslake
12
12
ms.reviewer: ninarn, carlrab
13
13
ms.date: 04/09/2020
14
14
---
15
-
# Elastic pools help you manage and scale multiple Azure SQL databases
15
+
# Elastic pools help you manage and scale multiple databases in Azure SQL Database
16
16
17
17
Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a single server and share a set number of resources at a set price. Elastic pools in Azure SQL Database enable SaaS developers to optimize the price performance for a group of databases within a prescribed budget while delivering performance elasticity for each database.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-pool-resource-management.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
@@ -117,5 +117,5 @@ FROM tempdb.sys.dm_db_log_space_usage;
117
117
118
118
## Next steps
119
119
120
-
- For an introduction to elastic pools, see [Elastic pools help you manage and scale multiple Azure SQL databases](https://docs.microsoft.com/azure/sql-database/sql-database-elastic-pool).
120
+
- For an introduction to elastic pools, see [Elastic pools help you manage and scale multiple databases in Azure SQL Database](https://docs.microsoft.com/azure/sql-database/sql-database-elastic-pool).
121
121
- For information on tuning query workloads to reduce resource utilization, see [Monitoring and tuning](https://docs.microsoft.com/azure/sql-database/sql-database-monitoring-tuning-index), and [Monitoring and performance tuning](https://docs.microsoft.com/azure/sql-database/sql-database-monitor-tune-overview).
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-query-overview.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The elastic query feature (in preview) enables you to run a Transact-SQL query t
21
21
22
22
### Azure SQL Database
23
23
24
-
Query across Azure SQL databases completely in T-SQL. This allows for read-only querying of remote databases and provides an option for current on-premises SQL Server customers to migrate applications using three- and four-part names or linked server to SQL Database.
24
+
Query across databases in Azure SQL Database completely in T-SQL. This allows for read-only querying of remote databases and provides an option for current on-premises SQL Server customers to migrate applications using three- and four-part names or linked server to SQL Database.
25
25
26
26
### Available on standard tier
27
27
@@ -61,7 +61,7 @@ Customer scenarios for elastic query are characterized by the following topologi
61
61
62
62
To begin coding, see [Getting started with cross-database query (vertical partitioning)](elastic-query-getting-started-vertical.md).
63
63
64
-
An elastic query can be used to make data located in a SQL database available to other SQL databases. This allows queries from one database to refer to tables in any other remote SQL database. The first step is to define an external data source for each remote database. The external data source is defined in the local database from which you want to gain access to tables located on the remote database. No changes are necessary on the remote database. For typical vertical partitioning scenarios where different databases have different schemas, elastic queries can be used to implement common use cases such as access to reference data and cross-database querying.
64
+
An elastic query can be used to make data located in a database in SQL Database available to other databases in SQL Database. This allows queries from one database to refer to tables in any other remote SQL database. The first step is to define an external data source for each remote database. The external data source is defined in the local database from which you want to gain access to tables located on the remote database. No changes are necessary on the remote database. For typical vertical partitioning scenarios where different databases have different schemas, elastic queries can be used to implement common use cases such as access to reference data and cross-database querying.
65
65
66
66
> [!IMPORTANT]
67
67
> You must possess ALTER ANY EXTERNAL DATA SOURCE permission. This permission is included with the ALTER DATABASE permission. ALTER ANY EXTERNAL DATA SOURCE permissions are needed to refer to the underlying data source.
@@ -73,13 +73,13 @@ An elastic query can be used to make data located in a SQL database available to
73
73
74
74
![Vertical partitioning - Using elastic query to query reference data][3]
75
75
76
-
**Cross-database querying**: Elastic queries enable use cases that require querying across several SQL databases. Figure 3 shows four different databases: CRM, Inventory, HR, and Products. Queries performed in one of the databases also need access to one or all the other databases. Using an elastic query, you can configure your database for this case by running a few simple DDL statements on each of the four databases. After this one-time configuration, access to a remote table is as simple as referring to a local table from your T-SQL queries or from your BI tools. This approach is recommended if the remote queries do not return large results.
76
+
**Cross-database querying**: Elastic queries enable use cases that require querying across several databases in SQL Database. Figure 3 shows four different databases: CRM, Inventory, HR, and Products. Queries performed in one of the databases also need access to one or all the other databases. Using an elastic query, you can configure your database for this case by running a few simple DDL statements on each of the four databases. After this one-time configuration, access to a remote table is as simple as referring to a local table from your T-SQL queries or from your BI tools. This approach is recommended if the remote queries do not return large results.
77
77
78
78
**Figure 3** Vertical partitioning - Using elastic query to query across various databases
79
79
80
80
![Vertical partitioning - Using elastic query to query across various databases][4]
81
81
82
-
The following steps configure elastic database queries for vertical partitioning scenarios that require access to a table located on remote SQL databases with the same schema:
82
+
The following steps configure elastic database queries for vertical partitioning scenarios that require access to a table located on remote databases in SQL Database with the same schema:
@@ -100,7 +100,7 @@ Using elastic query to perform reporting tasks over a sharded, that is, horizont
100
100
> Elastic Query Database (head node) can be separate database, or it can be the same database that hosts the shard map.
101
101
> Whatever configuration you choose, make sure that service tier and compute size of that database is high enough to handle the expected amount of login/query requests.
102
102
103
-
The following steps configure elastic database queries for horizontal partitioning scenarios that require access to a set of tables located on (typically) several remote SQL databases:
103
+
The following steps configure elastic database queries for horizontal partitioning scenarios that require access to a set of tables located on (typically) several remote databases in SQL Database:
Copy file name to clipboardExpand all lines: articles/azure-sql/database/elastic-scale-faq.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
@@ -24,7 +24,7 @@ Please see [Adding a shard to an application using the elastic database client l
24
24
25
25
## How much do elastic database tools cost
26
26
27
-
Using the elastic database client library does not incur any costs. Costs accrue only for the Azure SQL databases that you use for shards and the Shard Map Manager, as well as the web/worker roles you provision for the Split Merge tool.
27
+
Using the elastic database client library does not incur any costs. Costs accrue only for the databases in Azure SQL Database that you use for shards and the Shard Map Manager, as well as the web/worker roles you provision for the Split Merge tool.
28
28
29
29
## Why are my credentials not working when I add a shard from a different server
0 commit comments