Merge pull request #4641 from MicrosoftDocs/FromPublicRepo

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

Author: v-alje

docs/linux/sql-server-linux-change-repo.md

@@ -1,5 +1,5 @@
 ---
-title: Register the the General Availability repository for SQL Server on Linux | Microsoft Docs
+title: Register the General Availability repository for SQL Server on Linux | Microsoft Docs
 description: Change repositories from the preview SQL Server 2017 repository to the General Availability (GA) repository on Linux (GA is also sometimes referred to as RTM).
 author: annashres 
 ms.author: anshrest 

docs/relational-databases/spatial/spatial-indexes-overview.md

@@ -65,7 +65,7 @@ ms.workload: "On Demand"
 >  The grid densities of a spatial index are visible in the level_1_grid, level_2_grid, level_3_grid, and level_4_grid columns of the [sys.spatial_index_tessellations](../../relational-databases/system-catalog-views/sys-spatial-index-tessellations-transact-sql.md) catalog view when the database compatibility level is set to 100 or lower. The **GEOMETRY_AUTO_GRID**/**GEOGRAPHY_AUTO_GRID** tessellation scheme options do not populate these columns. sys.spatial_index_tessellations catalog view has **NULL** values for these columns when the auto grid options are used.  
   
 ###  <a name="tessellation"></a> Tessellation  
- After decomposition of an indexed space into a grid hierarchy, the spatial index reads the data from the spatial column, row by row. After reading the data for a spatial object (or instance), the spatial index performs a *tessellation process* for that object. The tessellation processfits the object into the grid hierarchy by associating the object with a set of grid cells that it touches (*touched cells*). Starting at level 1 of the grid hierarchy, the tessellation process proceeds *breadth first* across the level. Potentially, the process can continue through all four levels, one level at a time.  
+ After decomposition of an indexed space into a grid hierarchy, the spatial index reads the data from the spatial column, row by row. After reading the data for a spatial object (or instance), the spatial index performs a *tessellation process* for that object. The tessellation process fits the object into the grid hierarchy by associating the object with a set of grid cells that it touches (*touched cells*). Starting at level 1 of the grid hierarchy, the tessellation process proceeds *breadth first* across the level. Potentially, the process can continue through all four levels, one level at a time.  
 
  The output of the tessellation process is a set of touched cells that are recorded in the spatial index for the object. By referring to these recorded cells, the spatial index can locate the object in space relative to other objects in the spatial column that are also stored in the index.  
 

docs/relational-databases/stored-procedures/return-data-from-a-stored-procedure.md

@@ -26,7 +26,34 @@ ms.workload: "Active"
 [!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
  > For content related to previous versions of SQL Server, see [Return Data from a Stored Procedure](https://msdn.microsoft.com/en-US/library/ms188655(SQL.120).aspx).
 
-  There are two ways of returning result sets or data from a procedure to a calling program: output parameters and return codes. This topic provides information on both approaches.  
+  There are three ways of returning data from a procedure to a calling program: result sets, output parameters, and return codes. This topic provides information on the three approaches.  
+  
+  ## Returning Data Using Result Sets
+ If you include a SELECT statement in the body of a stored procedure (but not a SELECT ... INTO or INSERT ... SELECT), the rows specified by the SELECT statement will be sent directly to the client.  For large result sets the stored procedure execution will not continue to the next statement until the result set has been completely sent to the client.  For small result sets the results will be spooled for return to the client and execution will continue.  If multiple such SELECT statements are run during the exeuction of the stored proceudre, multiple result sets will be sent to the client.  This behavior also applies to nested TSQL batches, nested stored procedures and top-level TSQL batches.
+ 
+ 
+ ### Examples of Returning Data Using a Result Set 
+  The following example shows a stored procedure that returns the LastName and SalesYTD values for all SalesPerson rows that also appear in the vEmployee view.
+  
+ ```  
+USE AdventureWorks2012;  
+GO  
+IF OBJECT_ID('Sales.uspGetEmployeeSalesYTD', 'P') IS NOT NULL  
+    DROP PROCEDURE Sales.uspGetEmployeeSalesYTD;  
+GO  
+CREATE PROCEDURE Sales.uspGetEmployeeSalesYTD  
+AS    
+  
+    SET NOCOUNT ON;  
+    SELECT LastName, SalesYTD  
+    FROM Sales.SalesPerson AS sp  
+    JOIN HumanResources.vEmployee AS e ON e.BusinessEntityID = sp.BusinessEntityID  
+    
+RETURN  
+GO  
+  
+```  
+
 
 ## Returning Data Using an Output Parameter  
  If you specify the OUTPUT keyword for a parameter in the procedure definition, the procedure can return the current value of the parameter to the calling program when the procedure exits. To save the value of the parameter in a variable that can be used in the calling program, the calling program must use the OUTPUT keyword when executing the procedure. For more information about what data types can be used as output parameters, see [CREATE PROCEDURE (Transact-SQL)](../../t-sql/statements/create-procedure-transact-sql.md).  
@@ -110,7 +137,7 @@ GO
   
 ### Examples of Cursor Output Parameters  
  In the following example, a procedure is created that specified an output parameter, `@currency_cursor` using the **cursor** data type. The procedure is then called in a batch.  
-  
+ 
  First, create the procedure that declares and then opens a cursor on the Currency table.  
 
 ```  
@@ -157,7 +184,7 @@ DECLARE @result int;
 EXECUTE @result = my_proc;  
 ```  
 
- Return codes are commonly used in control-of-flow blocks within procedures to set the return code value for each possible error situation. You can use the @@ERROR function after a [!INCLUDE[tsql](../../includes/tsql-md.md)] statement to detect whether an error occurred during the execution of the statement.  
+ Return codes are commonly used in control-of-flow blocks within procedures to set the return code value for each possible error situation. You can use the @@ERROR function after a [!INCLUDE[tsql](../../includes/tsql-md.md)] statement to detect whether an error occurred during the execution of the statement.  Before the introduction of TRY/CATCH/THROW error handling in TSQL return codes were sometimes required to determine the success or failure of stored procedures.  Stored Procedures should always indicate failure with an error (generated with THROW/RAISERROR if neccessary), and not rely on a return code to indicate the failure.  Also you should avoid using the return code to return application data.
 
 ### Examples of Return Codes  
  The following example shows the `usp_GetSalesYTD` procedure with error handling that sets special return code values for various errors. The following table shows the integer value that is assigned by the procedure to each possible error, and the corresponding meaning for each value.  

docs/relational-databases/system-catalog-views/sys-column-store-segments-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.column_store_segments (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/30/2016"
+ms.date: "01/15/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "database-engine"
 ms.service: ""
@@ -43,8 +43,8 @@ Returns one row for each column segment in a columnstore index. There is one col
 |**encoding_type**|**int**|Type of encoding used for that segment:<br /><br /> 1 = VALUE_BASED     -  non-string/binary with no dictionary (very similar to 4 with some internal variations)<br /><br /> 2 = VALUE_HASH_BASED   - non-string/binary column with common values in dictionary<br /><br /> 3 = STRING_HASH_BASED  - string/binary column with common values in dictionary<br /><br /> 4 = STORE_BY_VALUE_BASED - non-string/binary with no dictionary<br /><br /> 5 = STRING_STORE_BY_VALUE_BASED - string/binary with no dictionary<br /><br /> All encodings take advantage of bit-packing and run-length encoding when possible.|  
 |**row_count**|**int**|Number of rows in the row group.|  
 |**has_nulls**|**int**|1 if the column segment has null values.|  
-|**base_id**|**bigint**|Base value id if encoding type 1 is being used.  If encoding type 1 is not being used, base_id is set to 1.|  
-|**magnitude**|**float**|Magnitude if encoding type 1 is being used.  If encoding type 1 is not being used, magnitude is set to 1.|  
+|**base_id**|**bigint**|Base value id if encoding type 1 is being used.  If encoding type 1 is not being used, base_id is set to -1.|  
+|**magnitude**|**float**|Magnitude if encoding type 1 is being used.  If encoding type 1 is not being used, magnitude is set to -1.|  
 |**primary_dictionary_id**|**int**|A value of 0 represents the global dictionary. A value of -1 indicates that there is no global dictionary created for this column.|  
 |**secondary_dictionary_id**|**int**|A non-zero value points to the local dictionary for this column in the current segment (i.e. the rowgroup). A value of -1 indicates that there is no local dictionary for this segment.|  
 |**min_data_id**|**bigint**|Minimum data id in the column segment.|  

docs/relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.sql_modules (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/17/2017"
+ms.date: "01/09/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
 ms.service: ""
@@ -38,7 +38,7 @@ ms.workload: "On Demand"
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**object_id**|**int**|ID of the object of the containing object. Is unique within a database.|  
-|**definition**|**nvarchar(max)**|SQL text that defines this module.<br /><br /> NULL = Encrypted.|  
+|**definition**|**nvarchar(max)**|SQL text that defines this module. This value can also be obtained using the [OBJECT_DEFINITION](../../t-sql/functions/object-definition-transact-sql.md) built-in function.<br /><br /> NULL = Encrypted.|  
 |**uses_ansi_nulls**|**bit**|Module was created with SET ANSI_NULLS ON.<br /><br /> Will always be = 0 for rules and defaults.|  
 |**uses_quoted_identifier**|**bit**|Module was created with SET QUOTED_IDENTIFIER ON.|  
 |**is_schema_bound**|**bit**|Module was created with SCHEMABINDING option.<br /><br /> Always contains a value of 1 for natively compiled stored procedures.|  

docs/relational-databases/system-dynamic-management-views/sys-dm-exec-sessions-transact-sql.md

@@ -107,6 +107,10 @@ Everyone can see their own session information.
 -   unsuccessful_logons  
 
  If this option is not enabled, these columns will return null values. For more information about how to set this server configuration option, see [common criteria compliance enabled Server Configuration Option](../../database-engine/configure-windows/common-criteria-compliance-enabled-server-configuration-option.md).  
+ 
+ 
+ The admin connections on Azure SQL Database will see one row per authenticated session, while the non-admin connections will only see information related to their database user sessions. 
+ 
 
 ## Relationship Cardinalities  
 

docs/relational-databases/system-stored-procedures/sp-rename-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sp_rename (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "01/09/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "database-engine, sql-database"
 ms.service: ""
@@ -81,9 +81,9 @@ sp_rename [ @objname = ] 'object_name' , [ @newname = ] 'new_name'
 
  sp_rename can be used to rename primary and secondary XML indexes.  
 
- Renaming a stored procedure, function, view, or trigger will not change the name of the corresponding object name in the definition column of the [sys.sql_modules](../../relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md) catalog view. Therefore, we recommend that sp_rename not be used to rename these object types. Instead, drop and re-create the object with its new name.  
+ Renaming a stored procedure, function, view, or trigger will not change the name of the corresponding object either in the definition column of the [sys.sql_modules](../../relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md) catalog view or obtained using the [OBJECT_DEFINITION](../../t-sql/functions/object-definition-transact-sql.md) built-in function. Therefore, we recommend that sp_rename not be used to rename these object types. Instead, drop and re-create the object with its new name.  
 
- Renaming an object such as a table or column will not automatically rename references to that object. You must modify any objects that reference the renamed object manually. For example, if you rename a table column and that column is referenced in a trigger, you must modify the trigger to reflect the new column name. Use[sys.sql_expression_dependencies](../../relational-databases/system-catalog-views/sys-sql-expression-dependencies-transact-sql.md) to list dependencies on the object before renaming it.  
+ Renaming an object such as a table or column will not automatically rename references to that object. You must modify any objects that reference the renamed object manually. For example, if you rename a table column and that column is referenced in a trigger, you must modify the trigger to reflect the new column name. Use [sys.sql_expression_dependencies](../../relational-databases/system-catalog-views/sys-sql-expression-dependencies-transact-sql.md) to list dependencies on the object before renaming it.  
 
 ## Permissions  
  To rename objects, columns, and indexes, requires ALTER permission on the object. To rename user types, requires CONTROL permission on the type. To rename a database, requires membership in the sysadmin or dbcreator fixed server roles  

docs/reporting-services/report-server/rsreportserver-config-configuration-file.md

@@ -71,7 +71,7 @@ For more information on editing the file, see [Modify a Reporting Services Confi
 |**LogonUser, LogonDomain, LogonCred**|Stores the domain, user name, and password of a domain account that is used by a report server to connect to a report server database. Values for **LogonUser**, **LogonDomain**, and **LogonCred** are created when the report server connection is configured to use a domain account. For more information about a report server database connection, see [Configure a Report Server Database Connection  (SSRS Configuration Manager)](../../reporting-services/install-windows/configure-a-report-server-database-connection-ssrs-configuration-manager.md).|N|  
 |**InstanceID**|An identifier for the report server instance. Report server instance names are based on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance names. This value specifies a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance name. By default, this value is **MSRS12***\<instancename>*. Do not modify this setting. The following is an example of the complete value: `<InstanceId>MSRS13.MSSQLSERVER</InstanceId>`<br /><br /> The following is an example of SharePoint mode:<br /><br /> `<InstanceId>MSRS12.@Sharepoint</InstanceId>`|N,S|  
 |**InstallationID**|An identifier for the report server installation that Setup creates. This value is set to a GUID. Do not modify this setting.|N|  
-|**SecureConnectionLevel**|Specifies the degree to which Web service calls must us Secure Sockets Layer (SSL). This setting is used for both the Report Server Web service and the web portal. This value is set when you configure a URL to use HTTP or HTTPS in the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool. Valid values range from 0 through 3, where 0 is least secure. For more information, see [Using Secure Web Service Methods](../../reporting-services/report-server-web-service/net-framework/using-secure-web-service-methods.md) and [Configure SSL Connections on a Native Mode Report Server](../../reporting-services/security/configure-ssl-connections-on-a-native-mode-report-server.md).|N,S|  
+|**SecureConnectionLevel**|Specifies the degree to which Web service calls must us Secure Sockets Layer (SSL). This setting is used for both the Report Server Web service and the web portal. This value is set when you configure a URL to use HTTP or HTTPS in the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool. In SQL Server 2008 R2, SecureConnectionLevel is made an on/off switch. For earlier versions than SQL Server 2008 R2 the valid values range are from 0 through 3, where 0 is least secure. For more information, see [ConfigurationSetting Method - SetSecureConnectionLevel](../../reporting-services/wmi-provider-library-reference/configurationsetting-method-setsecureconnectionlevel.md), [Using Secure Web Service Methods](../../reporting-services/report-server-web-service/net-framework/using-secure-web-service-methods.md) and [Configure SSL Connections on a Native Mode Report Server](../../reporting-services/security/configure-ssl-connections-on-a-native-mode-report-server.md).|N,S|
 |**DisableSecureFormsAuthenticationCookie**|Default value is False.<br /><br /> Specifies whether to disable the forcing of the cookie used for form and custom authentication to be marked secure. Starting with SQL Server 2012, [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] will automatically mark forms authentication cookies used with custom authentication extensions, as a secure cookie when sent to the client. By changing this property, report server administrators and custom security extension authors can revert to the previous behavior which allowed the custom security extension author to determine whether to mark the cookie as a secure cookie. It is recommended that secure cookies are used for forms authentication to help prevent network sniffing and replay attacks.|N|  
 |**CleanupCycleMinutes**|Specifies the number of minutes after which old sessions and expired snapshots are removed from the report server databases. Valid values range from 0 to maximum integer. The default is 10. Setting the value to 0 disables the database clean up the process.|N,S|  
 |**MaxActiveReqForOneUser**|Specifies the maximum number of reports that one user can process at the same time. Once the limit is reached, further report processing requests are denied. Valid values are 1 to a maximum integer. The default is 20.<br /><br /> Note that most requests process very quickly so it is unlikely that a single user will have more than 20 open connections at any given time. If users are opening more than 15 process-intensive reports at the same time, you might need to increase this value.<br /><br /> This setting is ignored for report servers that run in SharePoint integrated mode.|N,S|  

docs/reporting-services/wmi-provider-library-reference/configurationsetting-property-secureconnectionlevel.md

@@ -46,6 +46,10 @@ public Integer SecureConnectionLevel;
 ## Example Code  
  [MSReportServer_ConfigurationSetting Class](../../reporting-services/wmi-provider-library-reference/msreportserver-configurationsetting-class.md)  
 
+## Remarks
+
+In SQL Server 2008 R2, SecureConnectionLevel is made an on/off switch. For more information, see [ConfigurationSetting Method - SetSecureConnectionLevel](../../reporting-services/wmi-provider-library-reference/configurationsetting-method-setsecureconnectionlevel.md).
+
 ## Requirements  
  **Namespace:** [!INCLUDE[ssRSWMInmspcA](../../includes/ssrswminmspca-md.md)]