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/database/scale-resources.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article explains how to scale your database in Azure SQL Datab
4
4
author: dimitri-furman
5
5
ms.author: dfurman
6
6
ms.reviewer: wiassaf, mathoma, urmilano
7
-
ms.date: 05/21/2023
7
+
ms.date: 06/19/2023
8
8
ms.service: sql-db-mi
9
9
ms.subservice: performance
10
10
ms.topic: conceptual
@@ -41,9 +41,6 @@ The service tier, compute tier, and resource limits for a database, elastic pool
41
41
42
42
You can adjust the resources allocated to your database by changing service objective, or scaling, to meet workload demands. This also enables you to only pay for the resources that you need, when you need them. Please refer to the [note](#impact-of-scale-up-or-scale-down-operations) on the potential impact that a scale operation might have on an application.
43
43
44
-
> [!NOTE]
45
-
> Dynamic scaling is different from autoscaling. Autoscaling is when a service scales automatically based on criteria, whereas dynamic scaling allows for manual scaling with a minimal downtime. Single databases in Azure SQL Database can be scaled manually, or in the case of the [Serverless tier](serverless-tier-overview.md), set to automatically scale the compute resources. [Elastic pools](elastic-pool-overview.md), which allow databases to share resources in a pool, can currently only be scaled manually.
46
-
47
44
Azure SQL Database offers the ability to dynamically scale your databases:
48
45
49
46
- With a [single database](single-database-scale.md), you can use either [DTU](resource-limits-dtu-single-databases.md) or [vCore](resource-limits-vcore-single-databases.md) models to define maximum amount of resources that will be assigned to each database.
@@ -53,6 +50,11 @@ Azure SQL Managed Instance allows you to scale as well:
53
50
54
51
-[SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md) uses [vCores](../managed-instance/sql-managed-instance-paas-overview.md#vcore-based-purchasing-model) mode and enables you to define maximum CPU cores and maximum of storage allocated to your instance. All databases within the managed instance will share the resources allocated to the instance.
55
52
53
+
> [!TIP]
54
+
> Dynamic scaling lets customers change resource allocation manually or programmatically. The dynamic scaling capability is available for all Azure SQL Database and Azure SQL Managed Instance resources.
55
+
>
56
+
> In addition to supporting dynamic scaling, the [Serverless tier](serverless-tier-overview.md) in Azure SQL Database supports autoscaling. Databases in the Serverless tier scale resources automatically within a customer-specified range, based on workload demand. No customer action is required to scale the database.
57
+
56
58
## Impact of scale up or scale down operations
57
59
58
60
Initiating a scale up, or scale down action, in any of the flavors mentioned above, restarts the database engine process, and moves it to a different virtual machine if needed. Moving the database engine process to a new virtual machine is an **online process** during which you can continue using your existing Azure SQL Database service. Once the target database engine is ready to process queries, open connections to the current database engine will be [terminated](single-database-scale.md#impact), and uncommitted transactions will be rolled back. New connections will be made to the target database engine.
This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
1
+
---
2
+
author: rwestMSFT
3
+
ms.author: randolphwest
4
+
ms.date: 06/19/2023
5
+
ms.service: sql
6
+
ms.topic: include
7
+
---
8
+
This feature will be removed in a future version of [!INCLUDE [msconame-md](msconame-md.md)][!INCLUDE [ssnoversion-md](ssnoversion-md.md)]. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
This topic describes how to use built-in functions to view a saved trace.
17
-
18
-
### To view a specific trace
19
-
20
-
1. Execute **fn_trace_getinfo** by specifying the ID of the trace about which information is needed. This function returns a table that lists the trace, trace property, and information about the property.
21
-
22
-
Invoke the function this way:
23
-
24
-
```
25
-
SELECT *
26
-
FROM ::fn_trace_getinfo(trace_id)
27
-
```
28
-
29
-
### To view all existing traces
30
-
31
-
1. Execute **fn_trace_getinfo** by specifying `0` or `default`. This function returns a table that lists all the traces, their properties, and information about these properties.
32
-
33
-
Invoke the function as follows:
34
-
35
-
```
36
-
SELECT *
37
-
FROM ::fn_trace_getinfo(default)
38
-
```
39
-
40
-
## .NET Framework Security
41
-
To run the built-in function **fn_trace_getinfo**, the user needs the following permission:
This article describes how to use built-in functions to view a saved trace.
20
+
21
+
> [!IMPORTANT]
22
+
> [!INCLUDE[ssNoteDepFutureAvoid](../../includes/ssnotedepfutureavoid-md.md)] Use Extended Events instead.
23
+
24
+
## View a specific trace
25
+
26
+
1. Execute `sys.fn_trace_getinfo` by specifying the ID of the trace about which information is needed. This function returns a table that lists the trace, trace property, and information about the property.
27
+
28
+
Invoke the function this way:
29
+
30
+
```sql
31
+
SELECT*
32
+
FROM ::fn_trace_getinfo(trace_id);
33
+
```
34
+
35
+
## View all existing traces
36
+
37
+
1. Execute `sys.fn_trace_getinfo` by specifying `0` or `default`. This function returns a table that lists all the traces, their properties, and information about these properties.
Copy file name to clipboardExpand all lines: docs/sql-server/azure-arc/view-databases.md
+41-47Lines changed: 41 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,11 @@ title: View SQL Server databases
3
3
description: View databases in Azure from an instance of Azure Arc-enabled SQL Server. Use to inventory databases, and view properties of databases centrally, as Arc-enabled resources.
@@ -19,11 +18,11 @@ You can inventory and view SQL Server databases in Azure.
19
18
20
19
Before you begin, verify that the SQL Server instance that hosts the databases:
21
20
22
-
* Is hosted on a physical or virtual machine running Windows operating system.
23
-
* Is [!INCLUDE [sssql14-md](../../includes/sssql14-md.md)] or later.
24
-
* Is connected to Azure Arc. See [Connect your SQL Server to Azure Arc](connect.md).
25
-
* Is connected to the internet directly or through a proxy server.
26
-
21
+
- Is hosted on a physical or virtual machine running Windows operating system.
22
+
- Is [!INCLUDE [sssql14-md](../../includes/sssql14-md.md)] or later.
23
+
- Is connected to Azure Arc. See [Connect your SQL Server to Azure Arc](connect.md).
24
+
- Is connected to the internet directly or through a proxy server.
25
+
27
26
## Inventory databases
28
27
29
28
1. Locate the Azure Arc-enabled SQL Server instance in Azure portal
@@ -42,63 +41,63 @@ After you create, modify, or delete a database, changes are visible in Azure por
42
41
43
42
:::image type="content" source="media/view-databases/database-properties.png" alt-text="Screenshot of Azure portal, SQL Server database properties.":::
44
43
45
-
## How to Leverage Azure Resource Graph to Query Data
44
+
## How to use Azure Resource Graph to query data
46
45
47
-
Here are some example scenarios showing how you use [Azure Resource Graph](/azure/governance/resource-graph/overview)to query data which is available with the release of viewing Databases for Azure Arc-enabled SQL Server.
46
+
Here are some example scenarios showing how you use [Azure Resource Graph](/azure/governance/resource-graph/overview)to query data that is available with the release of viewing databases for Azure Arc-enabled SQL Server.
48
47
49
48
### Scenario 1: Get 10 databases
50
49
51
50
Get 10 databases and return what properties are available to query:
52
51
53
52
```kusto
54
-
Resources
53
+
resources
55
54
| where type =~ 'Microsoft.AzureArcData/sqlServerInstances/databases'
56
55
| limit 10
57
56
```
58
57
59
-
Many of the most interesting properties to query on are in the `properties` property. To explore the available properties run this query and then select **See details** on a row. This returns the properties in a json viewer on the right side.
58
+
Many of the most interesting properties to query on are in the `properties` property. To explore the available properties, run this query and then select **See details** on a row. This returns the properties in a json viewer on the right side.
60
59
61
60
```kusto
62
-
Resources
61
+
resources
63
62
| where type =~ 'Microsoft.AzureArcData/sqlServerInstances/databases'
64
63
| project properties
65
64
```
66
65
67
66
You can navigate the hierarchy of the properties json by using a period in between each level of the properties json.
68
67
69
-
### Scenario 2: Get all the databases that are not encrypted
68
+
### Scenario 2: Get all the databases that aren't encrypted
70
69
71
70
```kusto
72
-
Resources
71
+
resources
73
72
| where type =~ 'Microsoft.AzureArcData/sqlServerInstances/databases'
74
73
| where properties.databaseOptions.isEncrypted == false
75
74
```
76
75
77
-
### Scenario 3: Obtain the count of databases which are encrypted vs not encrypted
76
+
### Scenario 3: Obtain the count of databases that are encrypted vs not encrypted
|where type contains("microsoft.azurearcdata/sqlserverinstances/databases") and isEncrypted ==false
92
+
|project name,isEncrypted
94
93
```
95
94
96
95
### Scenario 5: Get all the databases by region and compatibility level
97
96
98
97
This example returns all databases in `westus3` location with compatibility level of 160:
99
98
100
99
```kusto
101
-
Resources
100
+
resources
102
101
| where type =~ 'Microsoft.AzureArcData/sqlServerInstances/databases'
103
102
| where location == "westus3"
104
103
| where properties.compatibilityLevel == "160"
@@ -107,44 +106,39 @@ Resources
107
106
### Scenario 6: Show the SQL Server version distribution
108
107
109
108
```kusto
110
-
Resources
111
-
|extend SQLversion =properties.version
112
-
|where type contains("microsoft.azurearcdata/sqlserverinstances")
113
-
|summarize count() by tostring(SQLversion)
109
+
resources
110
+
|extend SQLversion =properties.version
111
+
|where type contains("microsoft.azurearcdata/sqlserverinstances")
112
+
|summarize count() by tostring(SQLversion)
114
113
```
115
-
114
+
116
115
### Scenario 7: SQL Server by version, edition, and license type
117
116
118
117
```kusto
119
-
Resources
120
-
|extend SQLversion =properties.version
121
-
|extend SQLEdition =properties.edition
122
-
|extend lincentype =properties.licenseType
123
-
|where type contains("microsoft.azurearcdata/sqlserverinstances")
124
-
|project name,SQLversion,SQLEdition,lincensetype
118
+
resources
119
+
|extend SQLversion =properties.version
120
+
|extend SQLEdition =properties.edition
121
+
|extend lincentype =properties.licenseType
122
+
|where type contains("microsoft.azurearcdata/sqlserverinstances")
123
+
|project name,SQLversion,SQLEdition,lincentype
125
124
```
126
125
127
126
### Scenario 8: Show a count of databases by compatibility
128
127
129
128
This example returns the number of databases, ordered by the compatibility level:
130
129
131
130
```kusto
132
-
Resources
131
+
resources
133
132
| where type =~ 'Microsoft.AzureArcData/sqlServerInstances/databases'
134
133
| summarize count() by tostring(properties.compatibilityLevel)
135
134
| order by properties_compatibilityLevel asc
136
135
```
137
136
138
137
You can also [create charts and pin them to dashboards](/azure/governance/resource-graph/first-query-portal).
139
138
140
-
141
-
142
-
139
+
:::image type="content" source="media/view-databases/database-chart.png" alt-text="Diagram of a pie chart that displays the query results for the count of databases by compatibility level.":::
143
140
144
141
## Next steps
145
142
146
-
*[Protect Azure Arc-enabled SQL Server with Microsoft Defender for Cloud](configure-advanced-data-security.md)
0 commit comments