Skip to content

Commit 9920877

Browse files
committed
more
1 parent 9841bf7 commit 9920877

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

  • samples/manage/azure-sql-db-elastic-pools

samples/manage/azure-sql-db-elastic-pools/readme.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ This readme applies to the PowerShell scripts: PoolTelemetryJobRunner.ps1 and Po
2626
[Disclaimers](#disclaimers)<br/>
2727
[Related links](#related-links)<br/>
2828

29+
2930
<a name=what-do-the-powershell-scripts-do?></a>
3031

3132
## What do the PowerShell scripts do?
@@ -34,7 +35,7 @@ The scripts are used to extract telemetry data associated with SQL Database elas
3435

3536
There is a runner script, PoolTelemetryRunner.ps1, which needs to be modified for your environment to identify one or more servers on which elastic pools and databases are hosted and a telemetry database in which telemetry data is to be gathered. The runner script executes a function in the data collection script, PoolTelemetry.ps1 as a PowerShell job for each server.
3637

37-
Each data collection job executes in the background on a pre-determined schedule and will on first execution create the required schema in the telemetry database. It then connects to the master database on the server and retrieves elastic pool telemetry data and loads that to the telemetry database. It can optionally look back 14 days on first execution to get all available telemetry.
38+
Each data collection job executes in the background on a pre-determined schedule and will on first execution create the required schema in the telemetry database. It then connects to the master database on the server and retrieves elastic pool telemetry data and loads that to the telemetry database. It can optionally look back 14 days on first execution to get all available telemetry.
3839

3940
It then optionally queries the master database to determine the current elastic databases on the server, resident in each of the pools identified in the prior step. It then connects to each database in turn and retrieves and loads telemetry data for that database. It then sleeps for a period before waking up and repeating the data collection cycle.
4041

@@ -202,4 +203,4 @@ For more information, see these articles:
202203

203204
- [Monitor and manage an elastic database pool with Transact-SQL](https://azure.microsoft.com/documentation/articles/sql-database-elastic-pool-manage-tsql/)
204205

205-
- [Monitor and manage an elastic database pool with the Azure portal](https://azure.microsoft.com/documentation/articles/sql-database-elastic-pool-manage-portal/)
206+
- [Monitor and manage an elastic database pool with the Azure portal](https://azure.microsoft.com/documentation/articles/sql-database-elastic-pool-manage-portal/)

0 commit comments

Comments
 (0)