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
This article provides an overview of how to deploy [[!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)]](big-data-cluster-overview.md). It is meant to orient you to the concepts and provide a framework for understanding the other deployment articles in this section. Your specific deployment steps vary based on your platform choices for the client and server.
18
+
This article provides an overview of how to deploy [[!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)]](big-data-cluster-overview.md).
The article orients you to the concepts and provides a framework for understanding the other deployment articles in this section. Your specific deployment steps vary based on your platform choices for the client and server.
19
27
20
28
> [!TIP]
21
29
> To quickly get an environment with Kubernetes and big data cluster deployed to help you ramp up on its capabilities, use one of the sample scripts pointed to in [the scripts section](#scripts). After deployment, to manage the cluster use the [client tools](#tools) in the following section.
Copy file name to clipboardExpand all lines: docs/database-engine/install-windows/compatibility-certification.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
@@ -40,7 +40,7 @@ Using Compatibility Certification is a valuable approach to database modernizati
40
40
41
41
The possibility of adversely affecting functionality and performance are the main risk factors for any upgrade. Compatibility Certification represents peace of mind in terms of managing these upgrade risks:
42
42
43
-
- In what relates to [!INCLUDE[tsql](../../includes/tsql-md.md)] behavior, any change means that an application needs to be recertified for correctness. However, the [database compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md) setting provides backward compatibility with earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] only for the specified database, not for the entire server. Keeping the database compatibility level as-is ensures that existing application queries continue to display the same behavior before and after a [!INCLUDE[ssde_md](../../includes/ssde_md.md)] upgrade. For more information about [!INCLUDE[tsql](../../includes/tsql-md.md)] behavior and compatibility levels, see [Using compatibility levels for backward compatibility](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#using-compatibility-level-for-backward-compatibility).
43
+
- In what relates to [!INCLUDE[tsql](../../includes/tsql-md.md)] behavior, any change means that an application needs to be recertified for correctness. However, the [database compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md) setting provides backward compatibility with earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] only for the specified database, not for the entire server. Keeping the database compatibility level as-is ensures that existing application queries continue to display the same behavior before and after a [!INCLUDE[ssde_md](../../includes/ssde_md.md)] upgrade. For more information about [!INCLUDE[tsql](../../includes/tsql-md.md)] behavior and compatibility levels, see [Using compatibility levels for backward compatibility](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#backwardCompat).
44
44
45
45
- In what relates to performance, because improvements in the Query Optimizer are introduced with every version, it could be expected to encounter query plan differences between different [!INCLUDE[ssde_md](../../includes/ssde_md.md)] versions. Query plan differences in the scope of an upgrade usually translate to risk when there is potential that some changes may be detrimental for a given query or workload. In turn, this risk is a motivation for recertification, which can delay upgrades and pose lifecycle and support challenges.
46
46
Mitigating upgrade risks is why Query Optimizer improvements are gated to the default compatibility level of a new release. Compatibility Certification includes **query plan shape protection**: the notion that maintaining a database compatibility level as-is immediately after a [!INCLUDE[ssde_md](../../includes/ssde_md.md)] upgrade means that the query optimization model used to create query plans in the new version is the same as it was before the upgrade, and the query plan shape should not change.
@@ -49,7 +49,7 @@ The possibility of adversely affecting functionality and performance are the mai
49
49
> **Query plan shape** refers to the visual representation of the various operators that make up a query plan. This includes operators like seeks, scans, joins, and sorts, as well as the connections between them that indicate the flow of data and the order of the operations.
50
50
> The query plan shape is determined by the Query Optimizer. For more information, see the [Query Processing Architecture Guide](../../relational-databases/query-processing-architecture-guide.md#optimizing-select-statements).
51
51
52
-
For more information, see [Using compatibility levels for backward compatibility](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#using-compatibility-level-for-backward-compatibility).
52
+
For more information, see [Using compatibility levels for backward compatibility](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#backwardCompat).
53
53
54
54
As long as the application does not need to leverage enhancements that are only available in a higher database compatibility levels, it is a valid approach to upgrade the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] and maintain the previous database compatibility level, with no need to recertify an application. For more information, see [Compatibility levels and Database Engine upgrades](#compatibility-levels-and-database-engine-upgrades) later in this article.
Beginning with [!INCLUDE[sssql15](../../includes/sssql15-md.md)], [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] is only available as a 64-bit application. Here are important details about how to get SQL Server and how to install it.
21
+
22
+
This article provides guidance for installing SQL Server on Windows.
-[Kubernetes - Big Data Clusters](../../big-data-cluster/deploy-get-started.md)
29
+
30
+
Beginning with [!INCLUDE[sssql15](../../includes/sssql15-md.md)], [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] is only available as a 64-bit application. Here are important details about how to get SQL Server and how to install it.
This article explains how to configure and use the [mssql-server-linux container image](https://hub.docker.com/_/microsoft-mssql-server) with Docker. This image consists of SQL Server running on Linux based on Ubuntu 16.04. It can be used with the Docker Engine 1.8+ on Linux or on Docker for Mac/Windows.
18
+
This article explains how to configure and use the [mssql-server-linux container image](https://hub.docker.com/_/microsoft-mssql-server) with Docker.
-[Kubernetes - Big Data Clusters](../big-data-cluster/deploy-get-started.md)
25
+
26
+
This image consists of SQL Server running on Linux based on Ubuntu 16.04. It can be used with the Docker Engine 1.8+ on Linux or on Docker for Mac/Windows.
19
27
20
28
> [!NOTE]
21
29
> This article specifically focuses on using the mssql-server-linux image. The Windows image is not covered, but you can learn more about it on the [mssql-server-windows Docker Hub page](https://hub.docker.com/r/microsoft/mssql-server-windows-developer/).
Copy file name to clipboardExpand all lines: docs/relational-databases/performance/best-practice-with-the-query-store.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ ALTER DATABASE [QueryStoreDB]
65
65
SET QUERY_STORE (MAX_STORAGE_SIZE_MB =1024);
66
66
```
67
67
68
-
**Data Flush Interval (Minutes)**: Defines the frequency in seconds to persist collected runtime statistics to disk. The default is 900 seconds, which is 15 minutes. Consider using a higher value if your workload doesn't generate a large number of different queries and plans, or if you can withstand longer time to persist data before a database shutdown.
68
+
**Data Flush Interval (Minutes)**: It defines the frequency to persist collected runtime statistics to disk. It's expressed in minutes in the graphical user interface (GUI), but in [!INCLUDE[tsql](../../includes/tsql-md.md)] it's expressed in seconds. The default is 900 seconds, which is 15 minutes in the graphical user interface. Consider using a higher value if your workload doesn't generate a large number of different queries and plans, or if you can withstand longer time to persist data before a database shutdown.
69
69
70
70
> [!NOTE]
71
71
> Using trace flag 7745 prevents Query Store data from being written to disk in case of a failover or shutdown command. For more information, see the [Use trace flags on mission-critical servers to improve recovery from disaster](#Recovery) section.
@@ -77,14 +77,14 @@ ALTER DATABASE [QueryStoreDB]
77
77
SET QUERY_STORE (DATA_FLUSH_INTERVAL_SECONDS =900);
78
78
```
79
79
80
-
**Statistics Collection Interval**: Defines the level of granularity for the collected runtime statistic. The default is 60 minutes. Consider using a lower value if you require finer granularity or less time to detect and mitigate issues. Keep in mind that the value directly affects the size of Query Store data. Use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)] to set a different value for **Statistics Collection Interval**:
80
+
**Statistics Collection Interval**: Defines the level of granularity for the collected runtime statistic, expressed in minutes. The default is 60 minutes. Consider using a lower value if you require finer granularity or less time to detect and mitigate issues. Keep in mind that the value directly affects the size of Query Store data. Use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)] to set a different value for **Statistics Collection Interval**:
81
81
82
82
```sql
83
83
ALTERDATABASE [QueryStoreDB]
84
84
SET QUERY_STORE (INTERVAL_LENGTH_MINUTES =60);
85
85
```
86
86
87
-
**Stale Query Threshold (Days)**: Time-based cleanup policy that controls the retention period of persisted runtime statistics and inactive queries. By default, Query Store is configured to keep the data for 30 days, which might be unnecessarily long for your scenario.
87
+
**Stale Query Threshold (Days)**: Time-based cleanup policy that controls the retention period of persisted runtime statistics and inactive queries, expressed in days. By default, Query Store is configured to keep the data for 30 days, which might be unnecessarily long for your scenario.
88
88
89
89
Avoid keeping historical data that you don't plan to use. This practice reduces changes to read-only status. The size of Query Store data and the time to detect and mitigate the issue will be more predictable. Use [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] or the following script to configure time-based cleanup policy:
Copy file name to clipboardExpand all lines: docs/relational-databases/system-dynamic-management-views/sql-and-parallel-data-warehouse-dynamic-management-views.md
title: "sys.dm_pdw_nodes_exec_query_plan (Transact-SQL) | Microsoft Docs"
3
+
description: Dynamic management view that returns the Showplan in XML format for the batch specified by the plan handle. The plan specified by the plan handle can either be cached or currently executing.
Returns the Showplan in XML format for the batch specified by the plan handle. The plan specified by the plan handle can either be cached or currently executing.
|**pdw_node_id**|**int**|Unique numeric ID associated with the node.|
28
+
|**dbid**|**smallint**|ID of the context database that was in effect when the [!INCLUDE[tsql](../../includes/tsql-md.md)] statement corresponding to this plan was compiled. For unplanned and prepared SQL statements, the ID of the database where the statements were compiled.<br /><br /> Column is nullable.|
29
+
|**objectid**|**int**|ID of the object (for example, stored procedure or user-defined function) for this query plan. For ad hoc and prepared batches, this column is **null**.<br /><br /> Column is nullable.|
30
+
|**number**|**smallint**|Numbered stored procedure integer. For ad hoc and prepared batches, this column is **null**.<br /><br /> Column is nullable.|
31
+
|**encrypted**|**bit**|Indicates whether the corresponding stored procedure is encrypted.<br /><br /> 0 = not encrypted<br /><br /> 1 = encrypted<br /><br /> Column is not nullable.|
32
+
|**query_plan**|**xml**|Contains the compile-time Showplan representation of the query execution plan that is specified with *plan_handle*. The Showplan is in XML format. One plan is generated for each batch that contains, for example ad hoc [!INCLUDE[tsql](../../includes/tsql-md.md)] statements, stored procedure calls, and user-defined function calls.<br /><br /> Column is nullable.|
33
+
34
+
## Remarks
35
+
The same remarks in [sys.dm_exec_query_plan](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-query-plan-transact-sql?view=sql-server-ver15) apply.
36
+
37
+
## Permissions
38
+
Require **sysadmin** server role or `VIEW SERVER STATE` permission on the server.
39
+
40
+
## See also
41
+
[SQL Data Warehouse and Parallel Data Warehouse Dynamic Management Views (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sql-and-parallel-data-warehouse-dynamic-management-views.md)
42
+
43
+
## Next steps
44
+
For more development tips, see [SQL Data Warehouse development overview](https://docs.microsoft.com/azure/sql-data-warehouse/sql-data-warehouse-overview-develop).
0 commit comments