Merge pull request #20598 from MicrosoftDocs/master

11/02 AM Publish

Author: huypub

docs/connect/jdbc/using-table-valued-parameters.md

@@ -31,7 +31,7 @@ Column values in table-valued parameters can be accessed using standard Transact
 | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
 | [Table-Valued Parameters (Database Engine)](/previous-versions/sql/sql-server-2008/bb510489(v=sql.100)) in SQL Server Books Online | Describes how to create and use table-valued parameters                             |
 | [User-Defined Table Types](/previous-versions/sql/sql-server-2008/bb522526(v=sql.100)) in SQL Server Books Online                  | Describes user-defined table types that are used to declare table-valued parameters |
-| The [Microsoft SQL Server Database Engine](https://go.microsoft.com/fwlink/?LinkId=120507) section of CodePlex        | Contains samples that demonstrate how to use SQL Server features and functionality  |
+
 
 ## Passing multiple rows in previous versions of SQL Server  
 
@@ -309,4 +309,4 @@ The following methods have been added to this class to support passing of table-
 
 ## See also
 
-[Overview of the JDBC driver](overview-of-the-jdbc-driver.md)
+[Overview of the JDBC driver](overview-of-the-jdbc-driver.md)

docs/relational-databases/clr-integration-database-objects-user-defined-functions/clr-table-valued-functions.md

@@ -173,7 +173,7 @@ go
 ```  
 
 ## Sample: Returning the Results of a SQL Server Query  
- The following sample shows a table-valued function that queries a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. This sample uses the AdventureWorks Light database from [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)]. See [https://www.codeplex.com/sqlserversamples](https://go.microsoft.com/fwlink/?LinkId=87843) for more information on downloading AdventureWorks.  
+ The following sample shows a table-valued function that queries a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. This sample uses the AdventureWorks Lightweight database from [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], see the [AdventureWorks sample databases](/sql/samples/adventureworks-install-configure#download-backup-files)
 
  Name your source code file FindInvalidEmails.cs or FindInvalidEmails.vb.  
 

docs/relational-databases/clr-integration-database-objects-user-defined-types/creating-user-defined-types-coding.md

@@ -615,8 +615,6 @@ public void Rotate(double anglex, double angley, double anglez)
 
  The purpose of the padding is to ensure that the culture is completely separated from the currency value, so that when one UDT is compared against another in [!INCLUDE[tsql](../../includes/tsql-md.md)] code, culture bytes are compared against culture bytes, and currency byte values are compared against currency byte values.  
 
- For the complete code listing for the **Currency** UDT, follow the directions for installing the CLR samples in [SQL Server Database Engine Samples](https://msftengprodsamples.codeplex.com/).  
-  
 ### Currency Attributes  
  The **Currency** UDT is defined with the following attributes.  
 
@@ -739,9 +737,5 @@ public void Read(System.IO.BinaryReader r)
 }  
 ```  
 
- For the complete code listing for the **Currency** UDT, see [SQL Server Database Engine Samples](https://msftengprodsamples.codeplex.com/).  
-  
 ## See Also  
- [Creating a User-Defined Type](../../relational-databases/clr-integration-database-objects-user-defined-types/creating-user-defined-types.md)  
-  
-  
+ [Creating a User-Defined Type](../../relational-databases/clr-integration-database-objects-user-defined-types/creating-user-defined-types.md)  

docs/relational-databases/clr-integration-database-objects-user-defined-types/creating-user-defined-types.md

@@ -37,8 +37,6 @@ Reconfigure
 ## Example  
  The following code listing defines the Point UDT, which is described in detail in [Coding User-Defined Types](../../relational-databases/clr-integration-database-objects-user-defined-types/creating-user-defined-types-coding.md).  
 
- The complete code listings for the other examples discussed in this section can be obtained by installing the CLR samples. For instructions on installing these samples, see [SQL Server Database Engine Samples](https://msftengprodsamples.codeplex.com/).  
-  
  C#  
 
 ```  

docs/relational-databases/clr-integration/assemblies/creating-an-assembly.md

@@ -45,7 +45,7 @@ FROM 'C:\MyDBApp\SQLCLRTest.dll';
 -   The assembly that is called or referenced was created in the same database.  
 
 ## Specifying Security When Creating Assemblies  
- When creating an assembly into a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] database, you can specify one of three different levels of security in which your code can run: **SAFE**, **EXTERNAL_ACCESS**, or **UNSAFE**. When the **CREATE ASSEMBLY** statement is run, certain checks are performed on the code assembly which may cause the assembly to fail to register on the server. For more information, see the Impersonation sample on [CodePlex](https://msftengprodsamples.codeplex.com/).  
+ When creating an assembly into a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] database, you can specify one of three different levels of security in which your code can run: **SAFE**, **EXTERNAL_ACCESS**, or **UNSAFE**. When the **CREATE ASSEMBLY** statement is run, certain checks are performed on the code assembly which may cause the assembly to fail to register on the server.   
 
  **SAFE** is the default permission set and works for the majority of scenarios. To specify a given security level, you modify the syntax of the CREATE ASSEMBLY statement as follows:  
 

docs/relational-databases/databases/move-user-databases.md

@@ -1,8 +1,8 @@
 ---
 description: "Move User Databases"
-title: "Move User Databases | Microsoft Docs"
+title: "Move User Databases"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "11/02/2021"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.reviewer: ""
@@ -22,49 +22,60 @@ helpviewer_keywords:
   - "relocating database files"
   - "planned database relocations [SQL Server]"
   - "databases [SQL Server], moving"
-ms.assetid: ad9a4e92-13fb-457d-996a-66ffc2d55b79
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ---
 # Move User Databases
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
   In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you can move the data, log, and full-text catalog files of a user database to a new location by specifying the new file location in the FILENAME clause of the [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql.md) statement. This method applies to moving database files within the same instance [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. To move a database to another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or to another server, use [backup and restore](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md) or [detach and attach operations](../../relational-databases/databases/move-a-database-using-detach-and-attach-transact-sql.md).  
+
+> [!NOTE]
+> This article covers moving user database files. For moving system database files, see [Move System Databases](../../relational-databases/databases/move-system-databases.md).
   
 ## Considerations  
  When you move a database onto another server instance, to provide a consistent experience to users and applications, you might have to re-create some or all the metadata for the database. For more information, see [Manage Metadata When Making a Database Available on Another Server Instance (SQL Server)](../../relational-databases/databases/manage-metadata-when-making-a-database-available-on-another-server.md).  
 
- Some features of the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] change the way that the [!INCLUDE[ssDE](../../includes/ssde-md.md)] stores information in the database files. These features are restricted to specific editions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. A database that contains these features cannot be moved to an edition of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that does not support them. Use the sys.dm_db_persisted_sku_features dynamic management view to list all edition-specific features that are enabled in the current database.  
+ Some features of the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] change the way that the [!INCLUDE[ssDE](../../includes/ssde-md.md)] stores information in the database files. These features are restricted to specific editions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. A database that contains these features cannot be moved to an edition of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that does not support them. Use the `sys.dm_db_persisted_sku_features` dynamic management view to list all edition-specific features that are enabled in the current database.  
 
- The procedures in this topic require the logical name of the database files. To obtain the name, query the name column in the [sys.master_files](../../relational-databases/system-catalog-views/sys-master-files-transact-sql.md) catalog view.  
+ The procedures in this article require the logical name of the database files. To obtain the name, query the name column in the [sys.master_files](../../relational-databases/system-catalog-views/sys-master-files-transact-sql.md) catalog view.  
 
  Starting with [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], full-text catalogs are integrated into the database rather than being stored in the file system. The full-text catalogs now move automatically when you move a database.  
+
+> [!NOTE]
+> Make sure the service account for the [SQL Server Database Services service](../../database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md) has permissions to the new file location in the file system. For more information, see [Configure File System Permissions for Database Engine Access](../../database-engine/configure-windows/configure-file-system-permissions-for-database-engine-access.md).
   
 ## Planned Relocation Procedure  
  To move a data or log file as part of a planned relocation, follow these steps:  
 
 1.  For each file to be moved, run the following statement.  
 
-    ```  
+    ```sql  
     ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name, FILENAME = 'new_path\os_file_name' );  
     ```  
 
-2.  Run the following statement.  
+2.  Run the following statement to bring the database offline. 
 
-    ```  
+    ```sql  
     ALTER DATABASE database_name SET OFFLINE;  
     ```  
+
+    This action requires exclusive access to the database. If another connection is open to the database, the ALTER DATABASE statement will be blocked until all connections are closed. To override this behavior, use the [`WITH <termination>` clause](../../t-sql/statements/alter-database-transact-sql-set-options.md#with-termination-). For example, to automatically rollback and disconnect all other connections to the database, use:
+
+    ```sql
+    ALTER DATABASE database_name SET OFFLINE WITH ROLLBACK IMMEDIATE;  
+    ```
 
 3.  Move the file or files to the new location.  
 
 4.  Run the following statement.  
 
-    ```  
+    ```sql  
     ALTER DATABASE database_name SET ONLINE;  
     ```  
 
 5.  Verify the file change by running the following query.  
 
-    ```  
+    ```sql  
     SELECT name, physical_name AS CurrentLocation, state_desc  
     FROM sys.master_files  
     WHERE database_id = DB_ID(N'<database_name>');  
@@ -75,7 +86,7 @@ ms.author: wiassaf
 
 1.  For each file to be moved, run the following statement.  
 
-    ```  
+    ```sql  
     ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME = 'new_path\os_file_name' );  
     ```  
 
@@ -87,7 +98,7 @@ ms.author: wiassaf
 
 5.  Verify the file change by running the following query.  
 
-    ```  
+    ```sql  
     SELECT name, physical_name AS CurrentLocation, state_desc  
     FROM sys.master_files  
     WHERE database_id = DB_ID(N'<database_name>');  
@@ -105,21 +116,21 @@ ms.author: wiassaf
 
     -   For the default (MSSQLSERVER) instance, run the following command.  
 
-        ```  
+        ```console  
         NET START MSSQLSERVER /f /T3608  
         ```  
 
     -   For a named instance, run the following command.  
 
-        ```  
+        ```console  
         NET START MSSQL$instancename /f /T3608  
         ```  
 
      For more information, see [Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service](../../database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services.md).  
 
 3.  For each file to be moved, use **sqlcmd** commands or [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to run the following statement.  
 
-    ```  
+    ```sql  
     ALTER DATABASE database_name MODIFY FILE( NAME = logical_name , FILENAME = 'new_path\os_file_name' );  
     ```  
 
@@ -135,7 +146,7 @@ ms.author: wiassaf
 
 8.  Verify the file change by running the following query.  
 
-    ```  
+    ```sql  
     SELECT name, physical_name AS CurrentLocation, state_desc  
     FROM sys.master_files  
     WHERE database_id = DB_ID(N'<database_name>');  
@@ -144,7 +155,7 @@ ms.author: wiassaf
 ## Examples  
  The following example moves the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] log file to a new location as part of a planned relocation.  
 
-```  
+```sql  
 USE master;  
 GO  
 -- Return the logical file name.  
@@ -172,12 +183,13 @@ WHERE database_id = DB_ID(N'AdventureWorks2012')
 ```  
 
 ## See Also  
- [ALTER DATABASE &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-transact-sql.md)   
- [CREATE DATABASE &#40;SQL Server Transact-SQL&#41;](../../t-sql/statements/create-database-transact-sql.md)   
- [Database Detach and Attach &#40;SQL Server&#41;](../../relational-databases/databases/database-detach-and-attach-sql-server.md)   
- [Move System Databases](../../relational-databases/databases/move-system-databases.md)   
- [Move Database Files](../../relational-databases/databases/move-database-files.md)   
- [BACKUP &#40;Transact-SQL&#41;](../../t-sql/statements/backup-transact-sql.md)   
- [RESTORE &#40;Transact-SQL&#41;](../../t-sql/statements/restore-statements-transact-sql.md)   
- [Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service](../../database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services.md)  
+
+ - [ALTER DATABASE &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-transact-sql.md)   
+ - [CREATE DATABASE &#40;SQL Server Transact-SQL&#41;](../../t-sql/statements/create-database-transact-sql.md)   
+ - [Database Detach and Attach &#40;SQL Server&#41;](../../relational-databases/databases/database-detach-and-attach-sql-server.md)   
+ - [Move System Databases](../../relational-databases/databases/move-system-databases.md)   
+ - [Move Database Files](../../relational-databases/databases/move-database-files.md)   
+ - [BACKUP &#40;Transact-SQL&#41;](../../t-sql/statements/backup-transact-sql.md)   
+ - [RESTORE &#40;Transact-SQL&#41;](../../t-sql/statements/restore-statements-transact-sql.md)   
+ - [Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service](../../database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services.md)  
 

docs/relational-databases/databases/tempdb-database.md

@@ -1,8 +1,8 @@
 ---
 title: "tempdb database"
-description: This topic provides details about the configuration and use of the tempdb database in SQL Server and Azure SQL Database.
+description: This article provides details about the configuration and use of the tempdb database in SQL Server and Azure SQL Database.
 ms.custom: "P360"
-ms.date: 07/02/2021
+ms.date: 10/28/2021
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.technology: 
@@ -226,11 +226,12 @@ Metadata contention in `tempdb` has historically been a bottleneck to scalabilit
 
 This feature effectively removes this bottleneck and unlocks a new level of scalability for tempdb-heavy workloads. In [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], the system tables involved in managing temporary table metadata can be moved into latch-free, non-durable, memory-optimized tables.
 
+Currently the memory-optimized tempdb metadata feature is not available in Azure SQL Database or Azure SQL Managed Instance.
+
 Watch this seven-minute video for an overview of how and when to use memory-optimized tempdb metadata:
 
 > [!VIDEO https://channel9.msdn.com/Shows/Data-Exposed/How-and-When-To-Memory-Optimized-TempDB-Metadata/player?WT.mc_id=dataexposed-c9-niner]
 
-
 ### Configuring and using memory-optimized tempdb metadata
 
 To opt in to this new feature, use the following script:
@@ -342,10 +343,11 @@ SELECT R2.session_id,
 FROM sys.dm_db_session_space_usage AS R1
 INNER JOIN sys.dm_db_task_space_usage AS R2 ON R1.session_id = R2.session_id
 GROUP BY R2.session_id, R1.internal_objects_alloc_page_count,
-  R1.internal_objects_dealloc_page_count;;
+  R1.internal_objects_dealloc_page_count;
 ```
 
-## Related content
+## Next steps
+
 - [SORT_IN_TEMPDB option for indexes](../../relational-databases/indexes/sort-in-TempDB-option-for-indexes.md)    
 - [System databases](../../relational-databases/databases/system-databases.md)    
 - [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)    

docs/relational-databases/linked-servers/create-linked-servers-sql-server-database-engine.md

@@ -87,7 +87,7 @@ ms.custom: seo-dt-2019
      To use impersonation, the configuration must meet the requirement for delegation.  
 
      **Remote User**  
-     Use the remote user to map users not defined in **Local login**. The **Remote User** must be a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Authentication login on the remote server.  
+     Use the remote user to map user defined in **Local login**. The **Remote User** must be a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Authentication login on the remote server.  
 
      **Remote Password**  
      Specify the password of the Remote User.  

docs/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002.md

@@ -6,7 +6,7 @@ ms.prod: sql
 ms.prod_service: "database-engine"
 ms.reviewer: ""
 ms.technology: supportability
-ms.topic: conceptual
+ms.topic: troubleshooting
 helpviewer_keywords: 
   - "logs [SQL Server], full"
   - "troubleshooting [SQL Server], full transaction log"