Merge pull request #19639 from MicrosoftDocs/FromPublicRepo

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

Author: huypub

docs/azure-data-studio/extensions/sql-database-project-extension-build-from-command-line.md

@@ -19,19 +19,19 @@ While the SQL Database Project extension (preview) for Azure Data Studio provide
 
 1. Install and configure [SQL Database Projects extension for Azure Data Studio](sql-database-project-extension.md).
 
-2. The following .NET Core dlls and the target file `Microsoft.Data.Tools.Schema.SqlTasks.targets` are required to build a SQL database project from the command line from all platforms supported by the Azure Data Studio extension for SQL Database Projects. These files are created by the extension during the first build completed in the Azure Data Studio interface and placed in the extension's folder under `BuildDirectory`.  For example, on Linux, these files are placed in `~\.azuredatastudio\extensions\microsoft.sql-database-projects-x.x.x\BuildDirectory\`.  Copy these 10 files to a new and accessible folder or note their location.  This location will be referred to as `DotNet Core build folder` in this document.
+2. The following .NET Core dlls and the target file `Microsoft.Data.Tools.Schema.SqlTasks.targets` are required to build a SQL database project from the command line from all platforms supported by the Azure Data Studio extension for SQL Database Projects. These files are created by the extension during the first build completed in the Azure Data Studio interface and placed in the extension's folder under `BuildDirectory`.  For example, on Linux, these files are placed in `~\.azuredatastudio\extensions\microsoft.sql-database-projects-x.x.x\BuildDirectory\`.  Copy these 11 files to a new and accessible folder or note their location.  This location will be referred to as `DotNet Core build folder` in this document.
 
+    - Microsoft.Data.SqlClient.dll
     - Microsoft.Data.Tools.Schema.Sql.dll
+    - Microsoft.Data.Tools.Schema.SqlTasks.targets
     - Microsoft.Data.Tools.Schema.Tasks.Sql.dll
     - Microsoft.Data.Tools.Utilities.dll
-    - System.Io.Packaging.dll
     - Microsoft.SqlServer.Dac.dll
     - Microsoft.SqlServer.Dac.Extensions.dll
     - Microsoft.SqlServer.TransactSql.ScriptDom.dll
     - Microsoft.SqlServer.Types.dll
-    - Microsoft.Data.Tools.Schema.SqlTasks.targets
     - System.ComponentModel.Composition.dll
-    - Microsoft.Data.SqlClient.dll
+    - System.IO.Packaging.dll
 
 3. If the project was created in Azure Data Studio - skip ahead to [Build the project from the command line](#build-the-project-from-the-command-line). If the project was created in SQL Server Data Tools (SSDT), open the project in the Azure Data Studio SQL Database project extension.  Opening the project in Azure Data Studio automatically updates the `sqlproj` file with three edits, noted below for your information:
 

docs/relational-databases/system-functions/sys-fn-listextendedproperty-transact-sql.md

@@ -56,7 +56,23 @@ fn_listextendedproperty (
  Is the name of the property. *property_name* is **sysname**. Valid inputs are default, NULL, or a property name.  
 
  { default | '*level0_object_type*' | NULL}  
- Is the user or user-defined type. *level0_object_type* is **varchar(128)**, with a default of NULL. Valid inputs are ASSEMBLY, CONTRACT, EVENT NOTIFICATION, FILEGROUP, MESSAGE TYPE, PARTITION FUNCTION, PARTITION SCHEME, REMOTE SERVICE BINDING, ROUTE, SCHEMA, SERVICE, TRIGGER, TYPE, USER, and NULL.  
+ Is the user or user-defined type. *level0_object_type* is **varchar(128)**, with a default of NULL.  
+ Valid inputs are: 
+ - ASSEMBLY
+ - CONTRACT
+ - EVENT NOTIFICATION
+ - FILEGROUP
+ - MESSAGE TYPE
+ - PARTITION FUNCTION
+ - PARTITION SCHEME
+ - REMOTE SERVICE BINDING
+ - ROUTE
+ - SCHEMA
+ - SERVICE
+ - TRIGGER
+ - TYPE
+ - USER
+ - NULL  
 
 > [!IMPORTANT]  
 >  USER and TYPE as level-0 types will be removed in a future version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Avoid using these features in new development work, and plan to modify applications that currently use these features. Use SCHEMA as the level 0 type instead of USER. For TYPE, use SCHEMA as the level 0 type and TYPE as the level 1 type.  
@@ -65,7 +81,21 @@ fn_listextendedproperty (
  Is the name of the level 0 object type specified. *level0_object_name* is **sysname** with a default of NULL. Valid inputs are default, NULL, or an object name.  
 
  { default | '*level1_object_type*' | NULL }  
- Is the type of level 1 object. *level1_object_type* is **varchar(128)** with a default of NULL. Valid inputs are AGGREGATE, DEFAULT, FUNCTION, LOGICAL FILE NAME, PROCEDURE, QUEUE, RULE, SYNONYM, TABLE, TYPE, VIEW, XML SCHEMA COLLECTION, and NULL.  
+ Is the type of level 1 object. *level1_object_type* is **varchar(128)** with a default of NULL.  
+ Valid inputs are:
+ - AGGREGATE
+ - DEFAULT
+ - FUNCTION
+ - LOGICAL FILE NAME
+ - PROCEDURE
+ - QUEUE
+ - RULE
+ - SYNONYM
+ - TABLE
+ - TYPE
+ - VIEW
+ - XML SCHEMA COLLECTION
+ - NULL
 
 > [!NOTE]  
 >  Default maps to NULL and 'default' maps to the object type DEFAULT.  
@@ -74,7 +104,19 @@ fn_listextendedproperty (
  Is the name of the level 1 object type specified. *level1_object_name* is **sysname** with a default of NULL. Valid inputs are default, NULL, or an object name.  
 
  { default | '*level2_object_type*' |NULL }  
- Is the type of level 2 object. *level2_object_type* is **varchar(128)** with a default of NULL. Valid inputs are DEFAULT, default (maps to NULL), and NULL. Valid inputs for *level2_object_type* are COLUMN, CONSTRAINT, EVENT NOTIFICATION, INDEX, PARAMETER, TRIGGER, and NULL.  
+ Is the type of level 2 object. *level2_object_type* is **varchar(128)** with a default of NULL.  
+ Valid inputs are: 
+ - DEFAULT
+ - default (maps to NULL)
+ - NULL. 
+ Valid inputs for *level2_object_type* are: 
+ - COLUMN
+ - CONSTRAINT
+ - EVENT NOTIFICATION
+ - INDEX
+ - PARAMETER
+ - TRIGGER
+ - NULL
 
  { default | '*level2_object_name*' |NULL }  
  Is the name of the level 2 object type specified. *level2_object_name* is **sysname** with a default of NULL. Valid inputs are default, NULL, or an object name.  

docs/t-sql/statements/drop-database-transact-sql.md

@@ -97,7 +97,7 @@ The DROP DATABASE statement must run in autocommit mode and is not allowed in an
 You cannot drop a database currently being used. This means open for reading or writing by any user. One way to remove users from the database is to use ALTER DATABASE to set the database to SINGLE_USER.
 
 > [!WARNING]
-> This is not a fail-proof approach, since first consecutive connection made by any thread will receive the SINGLE_USER thread, causing your connection to fail. Sql server does not provide a built-in way to drop databases under load.
+> This is not a fail-proof approach, since first consecutive connection made by any thread will receive the SINGLE_USER thread, causing your connection to fail. SQL Server does not provide a built-in way to drop databases under load.
 
 ### [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
 
@@ -166,4 +166,4 @@ DROP DATABASE sales_snapshot0600;
 - [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql.md)
 - [CREATE DATABASE](../../t-sql/statements/create-database-transact-sql.md)
 - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md)
-- [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)
+- [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)