Merge pull request #17162 from MicrosoftDocs/master

9/24 AM Publish

Author: huypub

docs/machine-learning/install/custom-runtime-python.md

@@ -111,7 +111,7 @@ Append the instance name to `MSSQLLAUNCHPAD` (`MSSQLLAUNCHPAD$INSTANCENAME`). In
 2. Give permissions to **SID S-1-15-2-1**.
     ```cmd
     icacls "%PYTHONHOME%" /grant *S-1-15-2-1:(OI)(CI)RX /T
-    
+
 >[!NOTE]
 >The preceding command grants permissions to the computer **SID S-1-15-2-1**, which is equivalent to ALL APPLICATION PACKAGES on an English version of Windows. Alternatively, you can use `icacls "%R_HOME%" /grant "ALL APPLICATION PACKAGES":(OI)(CI)RX /T` on an English version of Windows.
 
@@ -128,7 +128,7 @@ Alternatively, right-click the SQL Server Launchpad service in the **Services**
 
 ## Download Python language extension
 
-Download the zip file containing the Python language extension, [python-lang-extension.zip](https://go.microsoft.com/fwlink/?linkid=2143952).
+Download the zip file containing the Python language extension, [python-lang-extension.zip](https://github.com/microsoft/sql-server-language-extensions/releases).
 
 ## Register external language
 
@@ -274,7 +274,7 @@ sudo systemctl restart mssql-launchpadd
 ```
 ## <a name="download-python-linux"></a> Download Python language extension
 
-Download the zip file containing the Python language extension, [python-lang-extension.zip](https://go.microsoft.com/fwlink/?linkid=2143793).
+Download the zip file containing the Python language extension, [python-lang-extension.zip](https://github.com/microsoft/sql-server-language-extensions/releases).
 
 ## Register external language
 

docs/machine-learning/install/custom-runtime-r.md

@@ -158,7 +158,7 @@ As an alternative, right-click the SQL Server Launchpad service in the **Service
 
 ## Download R language extension
 
-Download the zip file containing the R language extension [R-lang-extension.zip](https://go.microsoft.com/fwlink/?linkid=2143953).
+Download the zip file containing the R language extension [R-lang-extension.zip](https://github.com/microsoft/sql-server-language-extensions/releases).
 
 ## Register external language
 
@@ -337,7 +337,7 @@ sudo systemctl restart mssql-launchpadd
 
 ## Download R language extension
 
-Download the zip file containing the R language extension [R-lang-extension.zip](https://go.microsoft.com/fwlink/?linkid=2143954).
+Download the zip file containing the R language extension [R-lang-extension.zip](https://github.com/microsoft/sql-server-language-extensions/releases).
 
 ## Register external language
 

docs/relational-databases/databases/rebuild-system-databases.md

@@ -23,21 +23,23 @@ ms.author: "sstein"
 
  **In This Topic**  
 
--   **Before you begin:**  
+   - **Before you begin:**  
 
      [Limitations and Restrictions](#Restrictions)  
 
      [Prerequisites](#Prerequisites)  
 
--   **Procedures:**  
+   - **Procedures:**  
 
      [Rebuild System Databases](#RebuildProcedure)  
 
      [Rebuild the resource Database](#Resource)  
 
-     [Create a New msdb Database](#CreateMSDB)  
+     [Create a New msdb Database](#CreateMSDB) 
+
+     [Rebuild the tempdb Database](#RebuildTempdb)  
 
--   **Follow Up:**  
+   - **Follow Up:**  
 
      [Troubleshoot Rebuild Errors](#Troubleshoot)  
 
@@ -49,15 +51,15 @@ ms.author: "sstein"
 ###  <a name="Prerequisites"></a> Prerequisites  
  Perform the following tasks before you rebuild the system databases to ensure that you can restore the system databases to their current settings.  
 
-1.  Record all server-wide configuration values.  
+1. Record all server-wide configuration values.  
 
-    ```  
+    ```SQL  
     SELECT * FROM sys.configurations;  
     ```  
 
 2.  Record all hotfixes applied to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and the current collation. You must reapply these hotfixes after rebuilding the system databases.  
 
-    ```  
+    ```SQL  
     SELECT  
     SERVERPROPERTY('ProductVersion ') AS ProductVersion,  
     SERVERPROPERTY('ProductLevel') AS ProductLevel,  
@@ -68,7 +70,7 @@ ms.author: "sstein"
 
 3.  Record the current location of all data and log files for the system databases. Rebuilding the system databases installs all system databases to their original location. If you have moved system database data or log files to a different location, you must move the files again.  
 
-    ```  
+    ```SQL  
     SELECT name, physical_name AS current_file_location  
     FROM sys.master_files  
     WHERE database_id IN (DB_ID('master'), DB_ID('model'), DB_ID('msdb'), DB_ID('tempdb'));  
@@ -152,6 +154,7 @@ ms.author: "sstein"
 6.  From the **Ready to Repair** page, click **Repair**. The Complete page indicates that the operation is finished.  
 
 ##  <a name="CreateMSDB"></a> Create a New msdb Database  
+
  If the **msdb** database is damaged and you do not have a backup of the **msdb** database, you can create a new **msdb** by using the **instmsdb** script.  
 
 > [!WARNING]  
@@ -180,6 +183,33 @@ ms.author: "sstein"
 9. Recreate the user content stored in the **msdb** database, such as jobs, alert, etc.  
 
 10. Backup the **msdb** database.  
+
+##  <a name="RebuildTempdb"></a> Rebuild the Tempdb Database  
+
+If the **tempdb** database is damaged and the database engine fails to start, you can rebuild  **tempdb** without the need to rebuild all system databases.
+  
+1. Rename the current Tempdb.mdf and Templog.ldf files, if not missing. 
+1. Start [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from a Command Prompt by using the following command. 
+
+   ```sql
+   sqlservr -c -f -T3608 -T4022 -s <instance> -mSQLCMD
+   ```
+
+   For a default instance name use MSSQLSERVER, for named instance use MSSQL$<instance_name>. Trace flag 4022 disables execution of startup stored procedures. The -mSQLCMD allows only [sqlcmd.exe](../../ssms/scripting/sqlcmd-use-the-utility.md) to connect to the server (see [Other Startup Options](../../database-engine/configure-windows/database-engine-service-startup-options.md#other-startup-options))
+
+   > [!Note] 
+   > Make sure that the command prompt window remains open after the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] starts. Closing the command prompt window will terminate the process.
+
+1. Connect to the server by using **sqlcmd**, and then use the following stored procedure to reset the status of the tempdb database.
+
+   ```sql
+   exec master..sp_resetstatus Tempdb
+   ```
+
+1. Shut down the server by pressing CTRL+C in the command prompt window
+
+1. Restart the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service. This creates a new set of tempdb database files, and recovers the tempdb database.
+
 
 ##  <a name="Troubleshoot"></a> Troubleshoot Rebuild Errors  
  Syntax and other run-time errors are displayed in the command prompt window. Examine the Setup statement for the following syntax errors:  

docs/sql-server/azure-arc/media/overview/pubic-preview-architecture.png

@@ -8,6 +8,7 @@ ms.reviewer: mikeray
 ms.date: 09/10/2020
 ms.topic: conceptual
 ms.prod: sql
+ms.custom: references_regions
 ---
 
 # Azure Arc enabled SQL Server (preview)
@@ -20,7 +21,7 @@ The SQL Server can be installed in a virtual or physical machine running Windows
 
 The public preview of Azure Arc enabled SQL Server supports a set of solutions that require the Microsoft Monitoring Agent (MMA) server extension to be installed and connected to a Azure Log analytics workspace for data collection and reporting. These solutions include Advanced data security using Azure Security Center and Azure Sentinel, and SQL Environment health checks using On-demand SQL Assessment feature.
 
-The following diagram illustrates the architecture of Azure Arc enable SQL Server using the virtualized environment.
+The following diagram illustrates the architecture of Azure Arc enable SQL Server.
 
 ![Public preview architecture](media/overview/pubic-preview-architecture.png)
 

docs/sql-server/azure-arc/overview.md

@@ -126,6 +126,7 @@ The following table lists and describes the trace flags that are available in [!
 |**3625**|Limits the amount of information returned to users who are not members of the sysadmin fixed server role, by masking the parameters of some error messages using '\*\*\*\*\*\*'. This can help prevent disclosure of sensitive information.<br /><br />**Scope**: global only|  
 |**3656**|Enables symbol resolution on stack dumps when the Debugging Tools for Windows are installed. <br /><br />**WARNING:** This is a debugging trace flag and not meant for production environment use.<br /><br />**Note:** Starting with [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)], trace flag [2592](#2592) must be enabled in conjunction with trace flag 3656 to enable symbol resolution. <br/><br/>**Scope**: global and session|
 |**3924**|Enables automatic removal of orphaned DTC transactions with SPID=-2, which is a problem for some 3rd party transaction monitors. For more information, see this [Microsoft Support article](https://support.microsoft.com/help/4519668) and [Microsoft Support article](https://support.microsoft.com/help/4511816).<br /><br />**Scope**: global only|  
+|**4022**|Disables automatic execution of stored procedures when [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] starts. For more information about automatic execution of startup stored procedures see [sp_procoption](../../relational-databases/system-stored-procedures/sp-procoption-transact-sql.md) <br /><br />**Scope**: global only|  
 |**4136**|Disables parameter sniffing unless OPTION(RECOMPILE), WITH RECOMPILE or OPTIMIZE FOR \<value> is used. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/980653).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)], to accomplish this at the database level, see the PARAMETER_SNIFFING option in [ALTER DATABASE SCOPED CONFIGURATION &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />To accomplish the same result at the query level, add the OPTIMIZE FOR UNKNOWN [query hint](../../t-sql/queries/hints-transact-sql-query.md). The OPTIMIZE FOR UNKNOWN hint doesn't disable the parameter sniffing mechanism, but effectively bypasses it to achieve the same intended result.<br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, a second option to accomplish this at the query level is to add the USE HINT 'DISABLE_PARAMETER_SNIFFING' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global or session|  
 |**4137**|Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate a plan using minimum selectivity when estimating AND predicates for filters to account for partial correlation instead of independence, under the query optimizer cardinality estimation model of [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] and earlier versions (70). For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2658214).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'ASSUME_MIN_SELECTIVITY_FOR_FILTER_ESTIMATES' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag when using the CE 70.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag does not apply to CE version 120 or above. Use trace flag 9471 instead.<br /><br />**Scope**: global or session or query (QUERYTRACEON)| 
 |**4138**|Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate a plan that does not use row goal adjustments with queries that contain TOP, OPTION (FAST N), IN, or EXISTS keywords. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2667211).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'DISABLE_OPTIMIZER_ROWGOAL' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global or session or query (QUERYTRACEON)| 
@@ -159,7 +160,7 @@ The following table lists and describes the trace flags that are available in [!
 |**8048**|Converts NUMA partitioned memory objects into CPU partitioned. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2809338).<br /><br />**Note:** Starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2 and [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] this behavior is dynamic and controlled by the engine.<br /><br />**Scope**: global only|  
 |**8075**|Reduces [VAS](../../relational-databases/memory-management-architecture-guide.md#changes-to-memory-management-starting-2012-11x-gm) fragmentation when you receive memory page allocation errors on a 64-bit [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)]. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3074434).<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] RTM CU10, and [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP1 CU3. Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] this behavior is controlled by the engine and trace flag 8075 has no effect.<br /><br />**Scope**: global only|
 |**8079**|Allows [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2 to interrogate the hardware layout and automatically configure Soft-NUMA on systems reporting 8 or more CPUs per NUMA node. The automatic Soft-NUMA behavior is Hyperthread (HT/logical processor) aware. The partitioning and creation of additional nodes scales background processing by increasing the number of listeners, scaling and network and encryption capabilities.<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2. Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] this behavior is controlled by the engine and trace flag 8079 has no effect.<br /><br />**Scope**: global only| 
-|**8099**|Enables a spinlock contention fix for high-end systems running [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)] serving many concurrent users.<br /><br />**Note:** This trace flag applies to [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)] CU2 and higher builds. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4538688).<br /><br />**Scope**: global only| 
+|**8099**|Enables a spinlock contention fix for high-end systems running [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)] serving many concurrent users.<br /><br />**Note:** This trace flag applies to [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)] CU2 and CU3 only. Starting with [!INCLUDE[sql-server-2019](../../includes/sssqlv15-md.md)] CU4, this behavior is enabled by default. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4538688).<br /><br />**Scope**: global only| 
 |**8207**|Enables singleton updates for Transactional Replication and CDC. Updates to subscribers can be replicated as a DELETE and INSERT pair. This might not meet business rules, such as firing an UPDATE trigger. With trace flag 8207, an update to a unique column that affects only one row (a singleton update) is replicated as an UPDATE and not as a DELETE or INSERT pair. If the update affects a column on which a unique constraint exists, or if the update affects multiple rows, the update is still replicated as a DELETE or INSERT pair. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/302341).<br /><br />**Scope**: global only|
 |**8721**|Reports to the error log when auto-update statistics executes. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/195565).<br /><br />**Note:** This trace flag requires trace flag [3605](#3605) to be enabled.<br /><br />**Scope**: global only|
 |**8744**|Disable pre-fetching for the [Nested Loops](../../relational-databases/performance/joins.md#nested_loops) operator.<br /><br />**WARNING:** Incorrect use of this trace flag may cause additional physical reads when [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] executes plans that contain the Nested Loops operator.<br /><br />**Scope**: global and session|