Merge pull request #25417 from rwestMSFT/rw-1230-include-file-cleanup

INCLUDE file maintenance: move files around

Author: JamesJBarnett

docs/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2016.md

@@ -5,7 +5,7 @@ description: Learn about Database Engine changes in SQL Server 2016 (13.x) and e
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 07/25/2022
+ms.date: 12/30/2022
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: conceptual
@@ -20,7 +20,7 @@ helpviewer_keywords:
 
 This article describes breaking changes in the [!INCLUDE[sssql15-md](../includes/sssql16-md.md)] [!INCLUDE[ssDE](../includes/ssde-md.md)] and earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. You might encounter these issues when you upgrade.
 
-## <a id="SQL15"></a> Breaking Changes in [!INCLUDE[sssql15-md](../includes/sssql16-md.md)]
+## <a id="SQL15"></a> Breaking changes in SQL Server 2016
 
 - The *sample_ms* column of `sys.dm_io_virtual_file_stats` has expanded from an **int** to a **bigint** data type.
 
@@ -30,18 +30,18 @@ This article describes breaking changes in the [!INCLUDE[sssql15-md](../includes
 
 - Under database compatibility level 130, operations that perform implicit conversions between certain numeric and datetime data types show improved accuracy and can result in different converted values. This includes usage of functions that require calculations such as, for example, `DATEDIFF` and `ROUND`. For more information, see this [Microsoft Support Article](https://support.microsoft.com/help/4010261).
 
-## <a id="previous-versions"></a> Previous Versions
+## Previous versions
 
 For information about breaking changes in [!INCLUDE[ssSQL14](../includes/sssql14-md.md)], and in some earlier versions, see [Breaking Changes to Database Engine Features in SQL Server 2014](/previous-versions/sql/2014/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2016).
 
-#### Archived Documentation for Very Old Versions of SQL Server
+#### Archived documentation for old versions of SQL Server
 
-[!INCLUDE[Archived documentation for very old versions of SQL Server](../includes/paragraph-content/previous-versions-archive-documentation-sql-server.md)]
+[!INCLUDE[previous-versions-archive-documentation-sql-server](includes/previous-versions-archive-documentation-sql-server.md)]
 
 ## See also
 
 - [Deprecated Database Engine Features in SQL Server 2016](../database-engine/deprecated-database-engine-features-in-sql-server-2016.md)
 - [Discontinued Database Engine Functionality in SQL Server 2016](./discontinued-database-engine-functionality-in-sql-server.md)
 - [SQL Server Database Engine Backward Compatibility](./discontinued-database-engine-functionality-in-sql-server.md)
-- [ALTER DATABASE Compatibility Level &#40;Transact-SQL&#41;](../t-sql/statements/alter-database-transact-sql-compatibility-level.md)
+- [ALTER DATABASE Compatibility Level (Transact-SQL)](../t-sql/statements/alter-database-transact-sql-compatibility-level.md)
 - [SQL Server 2016 or SQL Server 2017 on Windows improvements in handling some data types and uncommon operations](https://support.microsoft.com/help/4010261)

docs/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2017.md

@@ -5,7 +5,7 @@ description: "Learn about changes that might break applications, scripts, or fun
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 07/25/2022
+ms.date: 12/30/2022
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: conceptual
@@ -20,7 +20,7 @@ monikerRange: ">=sql-server-2017||>=sql-server-linux-2017"
 
 This article describes breaking changes in the [!INCLUDE[sssql17-md](../includes/sssql17-md.md)] [!INCLUDE[ssDE](../includes/ssde-md.md)]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. You might encounter these issues when you upgrade.
 
-## Breaking changes in [!INCLUDE[sssql17-md](../includes/sssql17-md.md)] [!INCLUDE[ssDE](../includes/ssde-md.md)]
+## Breaking changes in SQL Server 2017 Database Engine
 
 - CLR uses Code Access Security (CAS) in the .NET Framework, which is no longer supported as a security boundary. Beginning with [!INCLUDE[sssql17-md](../includes/sssql17-md.md)] [!INCLUDE[ssDE](../includes/ssde-md.md)], an `sp_configure` option called `clr strict security` is introduced to enhance the security of CLR assemblies. clr strict security is enabled by default, and treats `SAFE` and `EXTERNAL_ACCESS` CLR assemblies as if they were marked `UNSAFE`. The `clr strict security` option can be disabled for backward compatibility, but this isn't recommended. When `clr strict security` is disabled, a CLR assembly created with `PERMISSION_SET = SAFE` may be able to access external system resources, call unmanaged code, and acquire **sysadmin** privileges. After enabling strict security, any assemblies that aren't signed will fail to load. Also, if a database has `SAFE` or `EXTERNAL_ACCESS` assemblies, `RESTORE` or `ATTACH DATABASE` statements can complete, but the assemblies may fail to load.
 
@@ -36,11 +36,11 @@ This article describes breaking changes in the [!INCLUDE[sssql17-md](../includes
 
 #### Archived documentation for old versions of SQL Server
 
-[!INCLUDE[Archived documentation for old versions of SQL Server](../includes/paragraph-content/previous-versions-archive-documentation-sql-server.md)]
+[!INCLUDE[previous-versions-archive-documentation-sql-server](includes/previous-versions-archive-documentation-sql-server.md)]
 
 ## See also
 
 - [Deprecated Database Engine Features in SQL Server 2016](../database-engine/deprecated-database-engine-features-in-sql-server-2016.md)
 - [Discontinued Database Engine Functionality in SQL Server 2016](./discontinued-database-engine-functionality-in-sql-server.md)
 - [SQL Server Database Engine Backward Compatibility](./discontinued-database-engine-functionality-in-sql-server.md)
-- [ALTER DATABASE Compatibility Level (Transact-SQL)](../t-sql/statements/alter-database-transact-sql-compatibility-level.md)
+- [ALTER DATABASE Compatibility Level (Transact-SQL)](../t-sql/statements/alter-database-transact-sql-compatibility-level.md)

…ions-archive-documentation-sql-server.md …ions-archive-documentation-sql-server.mddocs/includes/paragraph-content/previous-versions-archive-documentation-sql-server.md renamed to docs/database-engine/includes/previous-versions-archive-documentation-sql-server.md docs/includes/paragraph-content/previous-versions-archive-documentation-sql-server.md renamed to docs/database-engine/includes/previous-versions-archive-documentation-sql-server.md

@@ -1,14 +1,21 @@
-We accumulate and retain documentation for very old versions of Microsoft SQL Server, in sets of archived webpages. The archived webpages are not processed by search engines, such as Bing.com and Google.com. Yet you can see these archives at our Docs _previous-versions/sql/_ address:
+---
+author: rwestMSFT
+ms.author: randolphwest
+ms.date: 12/30/2022
+ms.service: sql
+ms.topic: include
+---
+We accumulate and retain documentation for very old versions of Microsoft SQL Server, in sets of archived webpages. The archived webpages are not processed by search engines, such as *bing.com* and *google.com*. Yet you can see these archives at our Docs *previous-versions/sql/* address:
 
 - [SQL Server previous versions documentation](/previous-versions/sql/)
 
 These archives include the documentation for at least the following older versions:
 
-- SQL Server 2014
-- SQL Server 2012
-- SQL Server 2008 R2
-- SQL Server 2008
-- SQL Server 2005
+- [!INCLUDE [sssql14-md](../../includes/sssql14-md.md)]
+- [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)]
+- [!INCLUDE [sql2008r2-md](../../includes/sql2008r2-md.md)]
+- [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)]
+- [!INCLUDE [ssversion2005-md](../../includes/ssversion2005-md.md)]
 
 [SQL Server 2014 documentation](/previous-versions/sql/2014/index?view=sql-server-2014&preserve-view=true) is still available on our main Docs address.
 
@@ -18,6 +25,6 @@ FYI: In the following link syntax to SQL 2014 content, the two 'view' related pa
 [SQL Server 2014 documentation](/previous-versions/sql/2014/index?view=sql-server-2014&preserve-view=true) is still available on our main Docs address.
 -->
 
-[SQL Server 2019 documentation](../../sql-server/index.yml?view=sql-server-ver15&preserve-view=true) is available on our main Docs address. Then use the versioning dropdown near the top of the page, to select another version of interest.
+[SQL Server 2022 documentation](../../sql-server/index.yml?view=sql-server-ver16&preserve-view=true) is available on our main Docs address. Then, you can use the versioning dropdown near the top of the page, to select another version of interest.
 
 For more information about the documentation for previous versions of SQL Server, see [Previous versions of SQL Server documentation](/previous-versions/sql/).

docs/includes/paragraph-content/sql-on-premises-vs-azure-similar-sys-views-include.md

@@ -1,29 +1,29 @@
-
-<!--
-### Code examples for Azure cloud differ slightly from on-premises
-  Or.....
-### Code examples can differ for Azure SQL Database
--->
-
+---
+author: rwestMSFT
+ms.author: randolphwest
+ms.date: 12/30/2022
+ms.service: sql-database
+ms.topic: include
+---
 Some Transact-SQL code examples written for SQL Server on-premises need small changes to run in the cloud. One category of such code examples involves system views whose name prefixes differ slightly between the two database systems:
 
-- **server\_** &nbsp; - &nbsp; _prefix for SQL Server and Azure SQL Managed Instance_
-- **database\_** &nbsp; - &nbsp; _prefix for Azure SQL Database and SQL Managed Instance_
+- **server_** - *prefix for SQL Server and Azure SQL Managed Instance*
+- **database_** - *prefix for Azure SQL Database and SQL Managed Instance*
 
 Azure SQL Database supports only database-scoped sessions. [SQL Server Management Studio](../../ssms/sql-server-management-studio-ssms.md) (SSMS) fully supports database-scoped sessions for Azure SQL Database: an **Extended Events** node containing database-scoped sessions appears under each database in [Object Explorer](../../ssms/object/object-explorer.md).
 
 Azure SQL Managed Instance supports both database-scoped sessions and server-scoped sessions. Server-scoped sessions are recommended for managed instances. SSMS fully supports server-scoped sessions for SQL Managed Instance: an **Extended Events** node containing all server-scoped sessions appears under the **Management** folder for each managed instance in Object Explorer.
 
-> [!NOTE]
+> [!NOTE]  
 > Database-scoped sessions are not displayed in Object Explorer in SSMS for Azure SQL Managed Instance. Database-scoped sessions may only be queried and managed with Transact-SQL when using a managed instance.
 
 For illustration, the following table lists and compares two subsets of the system views. For brevity, the subsets are restricted to view names that also contain the string `_event`. The subsets have differing name prefixes because they come from two different database systems.
 
 | Name from SQL Server | Name from cloud service |
-| :------------------------- | :---------------------- |
+| :--- | :--- |
 | server_event_notifications<br />server_event_session_actions<br />server_event_session_events<br />server_event_session_fields<br />server_event_session_targets<br />server_event_sessions<br />server_events<br />server_trigger_events | database_event_session_actions<br />database_event_session_events<br />database_event_session_fields<br />database_event_session_targets<br />database_event_sessions |
 
-The two lists in the preceding table are accurate as of March 2022. But the table contents here may become outdated, because they will not be maintained here. For accurate lists, refer to the following T-SQL SELECT statement.
+The two lists in the preceding table were accurate as of March 2022. For an accurate list, run the following Transact-SQL SELECT statement:
 
 ```sql
 SELECT name
@@ -35,4 +35,3 @@ SELECT name
         AND type = 'V'
     ORDER BY name;
 ```
-

docs/relational-databases/import-export/create-a-format-file-sql-server.md

@@ -27,7 +27,7 @@ Generally, XML and non-XML format files are interchangeable. However, we recomme
 > The version of the **bcp** utility (Bcp.exe) used to read a format file must be the same as, or later than the version used to create the format file. For example, [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] **bcp** can read a version 10.0 format file, which is generated by [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] **bcp**, but [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] **bcp** cannot read a version 11.0 format file, which is generated by [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] **bcp**.
 
 > [!NOTE]  
-> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE[Use ADF or PolyBase instead of Synapse Bulk Insert](../../includes/paragraph-content/bulk-insert-synapse.md)]
+> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
 ## Create a Non-XML format file
 

docs/relational-databases/import-export/format-files-for-importing-or-exporting-data-sql-server.md

@@ -23,7 +23,7 @@ When you bulk import data into a [!INCLUDE[ssNoVersion](../../includes/ssnoversi
 [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] supports two types of format files: XML formats and non-XML format files. Both non-XML format files and XML format files contain descriptions of every field in a data file, and XML format files also contain descriptions of the corresponding table columns. Generally, XML and non-XML format files are interchangeable. However, we recommend that you use the XML syntax for new format files because they provide several advantages over non-XML format files. For more information, see [XML Format Files (SQL Server)](../../relational-databases/import-export/xml-format-files-sql-server.md).
 
 > [!NOTE]  
-> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE[Use ADF or PolyBase instead of Synapse Bulk Insert](../../includes/paragraph-content/bulk-insert-synapse.md)]
+> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
 ## <a id="Benefits"></a> Benefits of format files
 

…paragraph-content/bulk-insert-synapse.md …t-export/includes/bulk-insert-synapse.mddocs/includes/paragraph-content/bulk-insert-synapse.md renamed to docs/relational-databases/import-export/includes/bulk-insert-synapse.md docs/includes/paragraph-content/bulk-insert-synapse.md renamed to docs/relational-databases/import-export/includes/bulk-insert-synapse.md

@@ -33,7 +33,7 @@ In [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)], two types of forma
 >  XML format files offer several advantages over non-XML format files. For more information, see [XML Format Files (SQL Server)](../../relational-databases/import-export/xml-format-files-sql-server.md).
 
 > [!NOTE]  
-> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE[Use ADF or PolyBase instead of Synapse Bulk Insert](../../includes/paragraph-content/bulk-insert-synapse.md)]
+> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
 ## <a id="Structure"></a> Structure of Non-XML Format Files
 

docs/relational-databases/import-export/non-xml-format-files-sql-server.md

@@ -30,7 +30,7 @@ This article illustrates the use of a format file in bulk-import operations.  A
   * [Load data into Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/design-elt-data-loading)
   * [Load data from SQL Server into Azure Synapse Analytics (flat files)](/azure/synapse-analytics/sql-data-warehouse/design-elt-data-loading)
   * [Migrate Your Data](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-develop)
-* This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE[Use ADF or PolyBase instead of Synapse Bulk Insert](../../includes/paragraph-content/bulk-insert-synapse.md)]
+* This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
 ## Example test conditions
 

docs/relational-databases/import-export/use-a-format-file-to-bulk-import-data-sql-server.md

@@ -23,7 +23,7 @@ A data file can contain fields arranged in a different order from the correspond
 > Either a non-XML or XML format file can be used to bulk import a data file into the table by using a [bcp utility](../../tools/bcp-utility.md) command, [BULK INSERT](../../t-sql/statements/bulk-insert-transact-sql.md) statement, or INSERT ... SELECT * FROM [OPENROWSET(BULK...)](../../t-sql/functions/openrowset-transact-sql.md) statement. For more information, see [Use a Format File to Bulk Import Data (SQL Server)](../../relational-databases/import-export/use-a-format-file-to-bulk-import-data-sql-server.md).
 
 > [!NOTE]  
-> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE[Use ADF or PolyBase instead of Synapse Bulk Insert](../../includes/paragraph-content/bulk-insert-synapse.md)]
+> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
 ## <a id="etc"></a> Example test conditions