Merge pull request #6905 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/relational-databases/import-export/import-data-from-excel-to-sql.md

@@ -1,4 +1,4 @@
----
+---
 title: "Import data from Excel to SQL | Microsoft Docs"
 ms.custom: ""
 ms.date: "06/29/2018"
@@ -24,7 +24,7 @@ There are several ways to import data from Excel files to SQL Server or to Azure
 
 -   You can import data in a single step, directly from Excel to SQL, by using one of the following tools:
     -   The [SQL Server Import and Export Wizard](#wiz)
-    -   ]SQL Server Integration Services (SSIS)](#ssis)
+    -   [SQL Server Integration Services (SSIS)](#ssis)
     -   The [OPENROWSET](#openrowset) function
 -   You can import data in two steps, by exporting your data from Excel as text, and then using one of the following tools to import the text file:
     -   The [Import Flat File Wizard](#import-wiz)

docs/relational-databases/system-catalog-views/sys-database-query-store-options-transact-sql.md

@@ -1,4 +1,4 @@
----
+---
 title: "sys.database_query_store_options (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
 ms.date: "10/25/2017"
@@ -37,9 +37,9 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**desired_state**|**smallint**|Indicates the desired operation mode of Query Store, explicitly set by user.<br /> 0 = OFF <br /> 1 = READ_ONLY<br /> 2 = READ_WRITE|  
-|**desired_state_desc**|**nvarchar(64)**|Textual description of the desired operation mode of Query Store:<br />OFF<br />READ_ONLY<br />READ_WRITE|  
+|**desired_state_desc**|**nvarchar(60)**|Textual description of the desired operation mode of Query Store:<br />OFF<br />READ_ONLY<br />READ_WRITE|  
 |**actual_state**|**smallint**|Indicates the operation mode of Query Store. In addition to list of desired states required by the user, actual state can be an error state.<br /> 0 = OFF <br /> 1 = READ_ONLY<br /> 2 = READ_WRITE<br /> 3 = ERROR|  
-|**actual_state_desc**|**nvarchar(64)**|Textual description of the actual operation mode of Query Store.<br />OFF<br />READ_ONLY<br />READ_WRITE<br />ERROR<br /><br /> There are situations when actual state is different from the desired state:<br /><br /> Query Store may operate in read-only mode even if read-write was specified by the user. For example, that might happen if the database is in read-only mode or if Query Store size exceeded the quota.<br /><br /> Extremely rarely, Query Store can end up in ERROR state because of internal errors. If this happens, Query Store could be recovered by executing **sp_query_store_consistency_check** stored procedure within the affected database.|  
+|**actual_state_desc**|**nvarchar(60)**|Textual description of the actual operation mode of Query Store.<br />OFF<br />READ_ONLY<br />READ_WRITE<br />ERROR<br /><br /> There are situations when actual state is different from the desired state:<br /><br /> Query Store may operate in read-only mode even if read-write was specified by the user. For example, that might happen if the database is in read-only mode or if Query Store size exceeded the quota.<br /><br /> Extremely rarely, Query Store can end up in ERROR state because of internal errors. If this happens, Query Store could be recovered by executing **sp_query_store_consistency_check** stored procedure within the affected database.|  
 |**readonly_reason**|**int**|When the **desired_state_desc** is READ_WRITE and the **actual_state_desc** is READ_ONLY, **readonly_reason** returns a bit map to indicate why the Query Store is in readonly mode.<br /><br /> 1 – database is in read-only mode<br /><br /> 2 – database is in single-user mode<br /><br /> 4 – database is in emergency mode<br /><br /> 8 – database is secondary replica (applies to Always On and Azure [!INCLUDE[ssSDS](../../includes/sssds-md.md)] geo-replication). This value can be effectively observed only on **readable** secondary replicas<br /><br /> 65536 – the Query Store has reached the size limit set by the MAX_STORAGE_SIZE_MB option.<br /><br /> 131072 - The number of different statements in Query Store has reached the internal memory limit. Consider removing queries that you do not need or upgrading to a higher service tier to enable transferring Query Store to read-write mode.<br />Only applies to [!INCLUDE[ssSDS](../../includes/sssds-md.md)].<br /><br /> 262144 – Size of in-memory items waiting to be persisted on disk has reached the internal memory limit. Query Store will be  in read-only mode temporarily until the in-memory items are persisted on disk. <br />Only applies to [!INCLUDE[ssSDS](../../includes/sssds-md.md)].<br /><br />524288 – Database has reached disk size limit. Query Store is part of user database, so if there is no more available space for a database, that means that Query Store cannot grow further anymore.<br />Only applies to [!INCLUDE[ssSDS](../../includes/sssds-md.md)]. <br /> <br /> To switch the Query Store operations mode back to read-write, see **Verify Query Store is Collecting Query Data Continuously** section of [Best Practice with the Query Store](../../relational-databases/performance/best-practice-with-the-query-store.md).|  
 |**current_storage_size_mb**|**bigint**|Size of Query Store on disk in megabytes.|  
 |**flush_interval_seconds**|**bigint**|Defines period for regular flushing of Query Store data to disk. Default value is 900 (15 min).<br /><br /> Change by using the `ALTER DATABASE <database> SET QUERY_STORE (DATA_FLUSH_INTERVAL_SECONDS  = <interval>)` statement.|  
@@ -49,8 +49,8 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 |**max_plans_per_query**|**bigint**|Limits the maximum number of stored plans. Default value is 200. If the maximum value is reached, Query Store stops capturing new plans for that query. Setting to 0 removes the limitation with regards to the number of captured plans.<br /><br /> Change by using the `ALTER DATABASE<database> SET QUERY_STORE (MAX_PLANS_PER_QUERY = <n>)` statement.|  
 |**query_capture_mode**|**smallint**|The currently active query capture mode:<br /><br /> 1 = ALL - all queries are captured. This is the default configuration value for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] ([!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] through [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]).<br /><br /> 2 = AUTO - capture relevant queries based on execution count and resource consumption. This is the default configuration value for [!INCLUDE[sqldbesa](../../includes/sqldbesa-md.md)].<br /><br /> 3 = NONE - stop capturing new queries. Query Store will continue to collect compile and runtime statistics for queries that were captured already. Use this configuration cautiously since you may miss to capture important queries.|  
 |**query_capture_mode_desc**|**nvarchar(60)**|Textual description of the actual capture mode of Query Store:<br /><br /> ALL (default for [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)])<br /><br /> AUTO (default for [!INCLUDE[sqldbesa](../../includes/sqldbesa-md.md)])<br /><br /> NONE|  
-|**size_based_cleanup_mode**|**smallint**|Controls whether cleanup will be automatically activated when total amount of data gets close to maximum size:<br /><br /> 1 = OFF – size based cleanup won’t be automatically activated.<br /><br /> 2 = AUTO - size based cleanup will be automatically activated when size on disk reaches 90% of **max_storage_size_mb**. This is the default configuration value.<br /><br />Size based cleanup removes the least expensive and oldest queries first. It stops at approximately 80% of max_storage_size_mb.|  
-|**size_based_cleanup_mode_desc**|**smallint**|Textual description of the actual size-based cleanup mode of Query Store:<br /><br /> OFF <br /><br /> AUTO (default)|  
+|**size_based_cleanup_mode**|**smallint**|Controls whether cleanup will be automatically activated when total amount of data gets close to maximum size:<br /><br /> 0 = OFF – size based cleanup won’t be automatically activated.<br /><br /> 1 = AUTO - size based cleanup will be automatically activated when size on disk reaches 90% of **max_storage_size_mb**. This is the default configuration value.<br /><br />Size based cleanup removes the least expensive and oldest queries first. It stops at approximately 80% of max_storage_size_mb.|  
+|**size_based_cleanup_mode_desc**|**nvarchar(60)**|Textual description of the actual size-based cleanup mode of Query Store:<br /><br /> OFF <br /><br /> AUTO (default)|  
 |**wait_stats_capture_mode**|**smallint**|Controls whether Query Store performs capture of wait statistics: <br /><br /> 0 = OFF <br /><br /> 1 = ON<br /> **Applies to**: [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] through [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)].|
 |**wait_stats_mode_capture_desc**|**nvarchar(60)**|Textual description of the actual wait statistics capture mode: <br /><br /> OFF <br /><br /> ON (default)<br /> **Applies to**: [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] through [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)].| 
 

docs/t-sql/functions/datediff-transact-sql.md

@@ -1,4 +1,4 @@
----
+---
 title: "DATEDIFF (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
 ms.date: "07/29/2017"
@@ -98,7 +98,7 @@ If *startdate* and *enddate* are both assigned only a time value, and the *datep
 
 `DATEDIFF` does not use a time zone offset component of *startdate* or *enddate* to calculate the return value.
 
-Because [smalldatetime](../../t-sql/data-types/smalldatetime-transact-sql.md) has accurate only to the minute, seconds and milliseconds are always set to 0 in the return value when *startdate* or *enddate* have a **smalldatetime** value.
+Because [smalldatetime](../../t-sql/data-types/smalldatetime-transact-sql.md) is accurate only to the minute, seconds and milliseconds are always set to 0 in the return value when *startdate* or *enddate* have a **smalldatetime** value.
 
 If only a time value is assigned to a date data type variable, `DATEDIFF` sets the value of the missing date part to the default value: 1900-01-01. If only a date value is assigned to a variable of a time or date data type, `DATEDIFF` sets the value of the missing time part to the default value: 00:00:00. If either *startdate* or *enddate* have only a time part and the other only a date part, `DATEDIFF` sets the missing time and date parts to the default values.
 

docs/t-sql/statements/restore-statements-verifyonly-transact-sql.md

@@ -118,6 +118,14 @@ FROM <backup_device> [ ,...n ]
   
 ### Permissions  
  Beginning in [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], obtaining information about a backup set or backup device requires CREATE DATABASE permission. For more information, see [GRANT Database Permissions &#40;Transact-SQL&#41;](../../t-sql/statements/grant-database-permissions-transact-sql.md).  
+ 
+## Examples  
+ The following example verifies the backup from disk.
+  
+```  
+RESTORE VERIFYONLY FROM DISK = 'D:\AdventureWorks.bak';
+GO
+```  
 
 ## See Also  
  [BACKUP &#40;Transact-SQL&#41;](../../t-sql/statements/backup-transact-sql.md)