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
@@ -42,10 +42,6 @@ Automatic tuning mechanisms are mature and have been perfected on several millio
42
42
43
43
Azure SQL Database automatic tuning is sharing its core logic with the SQL Server automatic tuning feature in the database engine. For additional technical information on the built-in intelligence mechanism, see [SQL Server automatic tuning](/sql/relational-databases/automatic-tuning/automatic-tuning).
44
44
45
-
For an overview of how automatic tuning works and for typical usage scenarios, see the embedded video:
- You [enable automatic tuning for Azure SQL Database in the Azure portal](automatic-tuning-enable.md) or by using the [ALTER DATABASE](/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azuresqldb-current&preserve-view=true) T-SQL statement.
@@ -67,7 +63,7 @@ Automatic tuning for Azure SQL Database uses the **CREATE INDEX**, **DROP INDEX*
67
63
68
64
You can either manually apply tuning recommendations using the Azure portal or you can let automatic tuning autonomously apply tuning recommendations for you. The benefits of letting the system autonomously apply tuning recommendations for you is that it automatically validates there exists a positive gain to the workload performance, and if there is no significant performance improvement detected, it will automatically revert the tuning recommendation. Please note that in case of queries affected by tuning recommendations that are not executed frequently, the validation phase can take up to 72 hrs by design.
69
65
70
-
In case you are applying tuning recommendations through T-SQL, the automatic performance validation, and reversal mechanisms are not available. Recommendations applied in such way will remain active and shown in the list of tuning recommendations for 24-48 hrs. before the system automatically withdraws them. If you would like to remove a recommendation sooner, you can discard it from Azure portal.
66
+
In case you are applying tuning recommendations through T-SQL, the automatic performance validation, and reversal mechanisms are not available. Recommendations applied in such way will remain active and shown in the list of tuning recommendations for 24-48 hours before the system automatically withdraws them. If you would like to remove a recommendation sooner, you can discard it from Azure portal.
71
67
72
68
Automatic tuning options can be independently enabled or disabled per database, or they can be configured at the server-level and applied on every database that inherits settings from the server. Servers can inherit Azure defaults for automatic tuning settings. Azure defaults at this time are set to FORCE_LAST_GOOD_PLAN is enabled, CREATE_INDEX is enabled, and DROP_INDEX is disabled.
@@ -36,14 +36,14 @@ From a database perspective, there are four major potential disruption scenarios
36
36
37
37
To mitigate the local hardware and software failures, SQL Database includes a [high availability architecture](high-availability-sla.md), which guarantees automatic recovery from these failures with up to 99.995% availability SLA.
38
38
39
-
To protect your business from data loss, SQL Database and SQL Managed Instance automatically create full database backups weekly, differential database backups every 12 hours, and transaction log backups every 5 - 10 minutes. The backups are stored in RA-GRS storage for at least 7 days for all service tiers. All service tiers except Basic support configurable backup retention period for point-in-time restore, up to 35 days.
39
+
To protect your business from data loss, SQL Database and SQL Managed Instance automatically create full database backups weekly, differential database backups every 12 hours, and transaction log backups every 5 - 10 minutes. The backups are stored in RA-GRS storage for at least seven days for all service tiers. All service tiers except Basic support configurable backup retention period for point-in-time restore, up to 35 days.
40
40
41
41
SQL Database and SQL Managed Instance also provide several business continuity features that you can use to mitigate various unplanned scenarios.
42
42
43
43
-[Temporal tables](../temporal-tables.md) enable you to restore row versions from any point in time.
44
44
-[Built-in automated backups](automated-backups-overview.md) and [Point in Time Restore](recovery-using-backups.md#point-in-time-restore) enables you to restore complete database to some point in time within the configured retention period up to 35 days.
45
45
- You can [restore a deleted database](recovery-using-backups.md#deleted-database-restore) to the point at which it was deleted if the **server has not been deleted**.
46
-
-[Long-term backup retention](long-term-retention-overview.md) enables you to keep the backups up to 10 years. This is in limited public preview for SQL Managed Instance
46
+
-[Long-term backup retention](long-term-retention-overview.md) enables you to keep the backups up to 10 years. This is in limited public preview for SQL Managed Instance.
47
47
-[Active geo-replication](active-geo-replication-overview.md) enables you to create readable replicas and manually failover to any replica in case of a datacenter outage or application upgrade.
48
48
-[Auto-failover group](auto-failover-group-overview.md#terminology-and-capabilities) allows the application to automatically recover in case of a datacenter outage.
49
49
@@ -78,9 +78,9 @@ Although rare, an Azure datacenter can have an outage. When an outage occurs, it
78
78
79
79
As you develop your business continuity plan, you need to understand the maximum acceptable time before the application fully recovers after the disruptive event. The time required for application to fully recover is known as Recovery time objective (RTO). You also need to understand the maximum period of recent data updates (time interval) the application can tolerate losing when recovering from an unplanned disruptive event. The potential data loss is known as Recovery point objective (RPO).
80
80
81
-
Different recovery methods offer different levels of RPO and RTO. You can choose a specific recovery method, or use a combination of methods to achieve full application recovery. The following table compares RPO and RTO of each recovery option. Auto-failover groups simplify the deployment and usage of geo-replication and adds the additional capabilities as described in the following table.
81
+
Different recovery methods offer different levels of RPO and RTO. You can choose a specific recovery method, or use a combination of methods to achieve full application recovery. The following table compares RPO and RTO of each recovery option. Auto-failover groups simplify the deployment and usage of geo-replication, and add the additional capabilities as described in the following table:
82
82
83
-
| Recovery method | RTO | RPO |
83
+
|**Recovery method**|**RTO**|**RPO**|
84
84
| --- | --- | --- |
85
85
| Geo-restore from geo-replicated backups | 12 h | 1 h |
86
86
| Auto-failover groups | 1 h | 5 s |
@@ -98,9 +98,6 @@ Use auto-failover groups if your application meets any of these criteria:
98
98
- Has a high rate of data change and 1 hour of data loss is not acceptable.
99
99
- The additional cost of active geo-replication is lower than the potential financial liability and associated loss of business.
You may choose to use a combination of database backups and active geo-replication depending upon your application requirements. For a discussion of design considerations for stand-alone databases and for elastic pools using these business continuity features, see [Design an application for cloud disaster recovery](designing-cloud-solutions-for-disaster-recovery.md) and [Elastic pool disaster recovery strategies](disaster-recovery-strategies-for-applications-with-elastic-pool.md).
105
102
106
103
The following sections provide an overview of the steps to recover using either database backups or active geo-replication. For detailed steps including planning requirements, post recovery steps, and information about how to simulate an outage to perform a disaster recovery drill, see [Recover a database in SQL Database from an outage](disaster-recovery-guidance.md).
@@ -109,7 +106,7 @@ The following sections provide an overview of the steps to recover using either
109
106
110
107
Regardless of the business continuity feature you use, you must:
111
108
112
-
- Identify and prepare the target server, including server-level IP firewall rules, logins, and master database level permissions.
109
+
- Identify and prepare the target server, including server-level IP firewall rules, logins, and `master` database level permissions.
113
110
- Determine how to redirect clients and client applications to the new server
114
111
- Document other dependencies, such as auditing settings and alerts
@@ -83,7 +83,7 @@ To download and run the sample, follow these steps:
83
83
84
84
3. Set the *ElasticScaleStarterKit* project as the Startup Project.
85
85
86
-
4. In the *ElasticScaleStarterKit* project, open the *App.config* file. Then follow the instructions in the file to add your server name and your sign-in information (username and password).
86
+
4. In the *ElasticScaleStarterKit* project, open the *App.config* file. Then follow the instructions in the file to add your server name and your signin information (username and password).
87
87
88
88
5. Build and run the application. When you are prompted, enable Visual Studio to restore the NuGet packages of the solution. This action downloads the latest version of the elastic database client library from NuGet.
89
89
@@ -129,7 +129,6 @@ For more information about Elastic Database Tools, see the following articles:
129
129
*[Elastic Database Tools for Azure SQL - Entity Framework Integration](https://code.msdn.microsoft.com/Elastic-Scale-with-Azure-bae904ba?SRC=VSIDE)
130
130
*[Shard Elasticity on Script Center](https://gallery.technet.microsoft.com/scriptcenter/Elastic-Scale-Shard-c9530cbe)
@@ -54,11 +54,6 @@ Identified database performance degradations are recorded in the SQLInsights log
54
54
| Root cause analysis | Root cause analysis of the issue identified in a human-readable format. Some insights might contain a performance improvement recommendation where possible. |
55
55
|||
56
56
57
-
For a hands-on overview on using Intelligent Insights with Azure SQL Analytics and for typical usage scenarios, see this video:
Intelligent Insights shines in discovering and troubleshooting database performance issues. In order to use Intelligent Insights to troubleshoot database performance issues, see [Troubleshoot performance issues with Intelligent Insights](intelligent-insights-troubleshoot-performance.md).
@@ -26,7 +26,7 @@ Azure SQL Database and Azure SQL Managed Instance let you parse and query data r
26
26
27
27
If you have a web service that takes data from the database layer and provides a response in JSON format, or client-side JavaScript frameworks or libraries that accept data formatted as JSON, you can format your database content as JSON directly in a SQL query. You no longer have to write application code that formats results from Azure SQL Database or Azure SQL Managed Instance as JSON, or include some JSON serialization library to convert tabular query results and then serialize objects to JSON format. Instead, you can use the FOR JSON clause to format SQL query results as JSON and use it directly in your application.
28
28
29
-
In the following example, rows from the Sales.Customer table are formatted as JSON by using the FOR JSON clause:
29
+
In the following example, rows from the `Sales.Customer` table are formatted as JSON by using the FOR JSON clause:
30
30
31
31
```sql
32
32
select CustomerName, PhoneNumber, FaxNumber
@@ -98,7 +98,7 @@ Instead of sending separate queries to get Customer data and then to fetch a lis
98
98
99
99
## Working with JSON data
100
100
101
-
If you don’t have strictly structured data, if you have complex sub-objects, arrays, or hierarchical data, or if your data structures evolve over time, the JSON format can help you to represent any complex data structure.
101
+
If you don't have strictly structured data, if you have complex sub-objects, arrays, or hierarchical data, or if your data structures evolve over time, the JSON format can help you to represent any complex data structure.
102
102
103
103
JSON is a textual format that can be used like any other string type in Azure SQL Database and Azure SQL Managed Instance. You can send or store JSON data as a standard NVARCHAR:
104
104
@@ -185,9 +185,3 @@ END
185
185
```
186
186
187
187
The collection of orders formatted as a JSON array and provided as a parameter to the stored procedure can be parsed and inserted into the Orders table.
188
-
189
-
## Next steps
190
-
191
-
To learn how to integrate JSON into your application, check out these resources:
192
-
193
-
To learn about various scenarios for integrating JSON into your application, see the demos in this [Channel 9 video](https://channel9.msdn.com/Events/DataDriven/SQLServer2016/JSON-as-a-bridge-betwen-NoSQL-and-relational-worlds) or find a scenario that matches your use case in [JSON Blog posts](/archive/blogs/sqlserverstorageengine/json-in-sql-server-use-cases).
Copy file name to clipboardExpand all lines: articles/azure-sql/database/monitoring-tuning-index.yml
+9-21Lines changed: 9 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
### YamlMime:Landing
2
2
3
-
title: Azure SQL Database and Azure SQL Managed Instance monitoring and performance tuning # < 60 chars
3
+
title: Azure SQL Database and Azure SQL Managed Instance monitoring and performance tuning
4
4
summary: Azure SQL Database and Azure SQL Managed Instance provide tools to help you collect metrics and diagnostic information to monitor your database and improve its performance. # < 160 chars
5
5
6
6
metadata:
7
-
title: Azure SQL Database and Azure SQL Managed Instance monitoring and tuning documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
7
+
title: Azure SQL Database and Azure SQL Managed Instance monitoring and tuning documentation
8
8
description: Learn about Azure SQL Database monitoring and performance tuning tools that help you collect metrics and diagnostics and improve database performance.
9
-
ms.service: sql-database #Required; service per approved list. service slug assigned to your service by ACOM.
10
-
ms.subservice: performance # Optional; Remove if no subservice is used.
9
+
ms.service: sql-database
10
+
ms.subservice: performance
11
11
ms.custom: sqldbrb=2
12
-
ms.topic: landing-page # Required
13
-
ms.collection: performance# Optional; Remove if no collection is used.
14
-
author: WilliamDAssafMSFT #Required; your GitHub user alias, with correct capitalization.
15
-
ms.author: wiassaf #Required; microsoft alias of author; optional team alias.
> Under some circumstances, you may need to shrink a database to reclaim unused space. For more information, see [Manage file space in Azure SQL Database](file-space-manage.md).
0 commit comments