Skip to content

new-updated-t-sql.md

Latest commit

 

History

History
205 lines (108 loc) · 9.07 KB

new-updated-t-sql.md

File metadata and controls

205 lines (108 loc) · 9.07 KB
title Updated - T-SQL docs | Microsoft Docs
description Display snippets of updated content for recently changed in documentation, for Transact-SQL.
manager craigg
author MightyPen
ms.author genemi
ms.topic article
ms.custom UpdArt.exe
ms.suite sql
ms.technology release-landing
ms.prod sql
ms.prod_service sql-non-specified
ms.component t-sql
ms.date 04/28/2018

New and Recently Updated: Transact-SQL docs

Nearly every day Microsoft updates some of its existing articles on its Docs.Microsoft.com documentation website. This article displays excerpts from recently updated articles. Links to new articles might also be listed.

This article is generated by a program that is rerun periodically. Occasionally an excerpt can appear with imperfect formatting, or as markdown from the source article. Images are never displayed here.

Recent updates are reported for the following date range and subject:

  • Date range of updates:   2018-02-03   -to-   2018-04-28
  • Subject area:   T-SQL.

 

New Articles Created Recently

The following links jump to new articles that have been added recently.

There are no new articles to list, this time.

 

Updated Articles with Excerpts

This section displays the excerpts of updates gathered from articles that have recently experienced a large update.

The excerpts displayed here appear separated from their proper semantic context. Also, sometimes an excerpt is separated from important markdown syntax that surrounds it in the actual article. Therefore these excerpts are for general guidance only. The excerpts only enable you to know whether your interests warrant taking the time to click and visit the actual article.

For these and other reasons, do not copy code from these excerpts, and do not take as exact truth any text excerpt. Instead, visit the actual article.

 

Compact List of Articles Updated Recently

This compact list provides links to all the updated articles that are listed in the Excerpts section.

  1. ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)
  2. RESTORE Statements (Transact-SQL)

 

 

1.   ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)

Updated: 2018-04-13           (Next)

 

XTP_PROCEDURE_EXECUTION_STATISTICS = { ON | OFF }

Applies to: {Included-Content-Goes-Here}

Enables or disables collection of execution statistics at the module-level for natively compiled T-SQL modules in the current database. The default is OFF. The execution statistics are reflected in [sys.dm_exec_procedure_stats].

Module-level execution statistics for natively compiled T-SQL modules are collected if either this option is ON, or if statistics collection is enabled through [sp_xtp_control_proc_exec_stats].

XTP_QUERY_EXECUTION_STATISTICS = { ON | OFF }

Applies to: {Included-Content-Goes-Here}

Enables or disables collection of execution statistics at the statement-level for natively compiled T-SQL modules in the current database. The default is OFF. The execution statistics are reflected in [sys.dm_exec_query_stats] and in [Query Store].

Statement-level execution statistics for natively compiled T-SQL modules are collected if either this option is ON, or if statistics collection is enabled through [sp_xtp_control_query_exec_stats].

For more details about performance monitoring of natively-compiled T-SQL modules see [Monitoring Performance of Natively Compiled Stored Procedures].

 

 

2.   RESTORE Statements (Transact-SQL)

Updated: 2018-04-13           (Previous)

 

General Remarks - SQL Database Managed Instance

For an asynchronous restore, the restore continues even if client connection breaks. If your connection is dropped, you can check [sys.dm_operation_status] view for the status of a restore operation (as well as for CREATE and DROP database).

The following database options are set/overridden and cannot be changed later:

  • NEW_BROKER (if broker is not enabled in .bak file)
  • ENABLE_BROKER (if broker is not enabled in .bak file)
  • AUTO_CLOSE=OFF (if a database in .bak file has AUTO_CLOSE=ON)
  • RECOVERY FULL (if a database in .bak file has SIMPLE or BULK_LOGGED recovery mode)
  • Memory optimized filegroup is added and called XTP if it was not in the source .bak file. Any existing memory optimized filegroup is renamed to XTP
  • SINGLE_USER and RESTRICTED_USER options are converted to MULTI_USER

Limitations - SQL Database Managed Instance

These limitations apply:

  • .BAK files containing multiple backup sets cannot be restored.
  • .BAK files containing multiple log files cannot be restored.
  • Restore will fail if .bak contains FILESTREAM data.
  • Backups containing databases that have active In-memory objects cannot currently be restored.
  • Backups containing databases where at some point In-Memory objects existed cannot currently be restored.
  • Backups containing databases in read-only mode cannot currently be restored. This limitation will be removed soon.

For more information, see [Managed Instance]

Similar articles about new or updated articles

This section lists very similar articles for recently updated articles in other subject areas, within our public GitHub.com repository: MicrosoftDocs/sql-docs.

Subject areas that do have new or recently updated articles

Subject areas that do not have any new or recently updated articles