Merge pull request #18629 from MicrosoftDocs/master

2/17 AM Publish

Author: huypub

docs/connect/spark/connector.md

@@ -20,7 +20,14 @@ This library contains the source code for the Apache Spark Connector for SQL Ser
 
 [Apache Spark](https://spark.apache.org/) is a unified analytics engine for large-scale data processing.
 
-You can get the connector from [Maven](https://search.maven.org/search?q=spark-mssql-connector). To import the connector, use the coordinate `com.microsoft.azure:spark-mssql-connector:<latest version>`. You can also build the connector from source or download the jar from the Release section in GitHub. For the latest information about the connector, see [SQL Spark connector GitHub repository](https://github.com/microsoft/sql-spark-connector).
+There are two versions of the connector available through Maven, a 2.4.5 compatible version and a 3.0.0 compatible version. Both versions can be found [here](https://search.maven.org/search?q=spark-mssql-connector) and can be imported using the coordinates below:
+
+| Connector | Maven Coordinate |
+| --------- | ------------------ |
+| Spark 2.4.5 compatible connnector | `com.microsoft.azure:spark-mssql-connector:1.0.1` |
+| Spark 3.0.0 compatible connnector | `com.microsoft.azure:spark-mssql-connector_2.12_3.0:1.0.0-alpha` |
+
+You can also build the connector from source or download the jar from the Release section in GitHub. For the latest information about the connector, see [SQL Spark connector GitHub repository](https://github.com/microsoft/sql-spark-connector).
 
 ## Supported Features
 
@@ -32,8 +39,8 @@ You can get the connector from [Maven](https://search.maven.org/search?q=spark-m
 
 | Component                            | Versions Supported              |
 |--------------------------------------|---------------------------------|
-| Apache Spark                         | 2.4.5 (Spark 3.0 not supported) |
-| Scala                                | 2.11                            |
+| Apache Spark                         | 2.4.5, 3.0.0 |
+| Scala                                | 2.11, 2.12                            |
 | Microsoft JDBC Driver for SQL Server | 8.2                             |
 | Microsoft SQL Server                 | SQL Server 2008 or later        |
 | Azure SQL Databases                  | Supported                       |

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

@@ -42,20 +42,20 @@ ms.author: "sstein"
 ## Planned Relocation Procedure  
  To move a data or log file as part of a planned relocation, follow these steps:  
 
-1.  Run the following statement.  
+1.  For each file to be moved, run the following statement.  
 
     ```  
-    ALTER DATABASE database_name SET OFFLINE;  
+    ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name, FILENAME = 'new_path\os_file_name' );  
     ```  
   
-2.  Move the file or files to the new location.  
-  
-3.  For each file moved, run the following statement.  
+2.  Run the following statement.  
   
     ```  
-    ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name, FILENAME = 'new_path\os_file_name' );  
+    ALTER DATABASE database_name SET OFFLINE;  
     ```  
   
+3.  Move the file or files to the new location.  
+  
 4.  Run the following statement.  
   
     ```  

docs/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md

@@ -106,6 +106,8 @@ For more information, see [Manage Access to Azure Storage Resources](/azure/stor
 
 ###  <a name="bkmk_Limitations"></a> Limitations  
 
+- Due to the performance characteristics of SQL Server workloads, SQL Server data files are implemented as page blobs in Azure Blob Storage. Other types of blob storage such as block blobs or [Azure Data Lake Storage](https://docs.microsoft.com/azure/storage/blobs/data-lake-storage-introduction) are not supported.
+
 - In the current release of this feature, storing **FileStream** data in Azure Storage is not supported. You can store **FileStream** data in a database that also contains data files stored in Azure Storage, but all FileStream data files must be stored on local storage.  Since the FileStream data must reside on local storage, it cannot be moved between machines using Azure Storage, therefore we recommend that you continue using the [traditional techniques](../../relational-databases/blob/move-a-filestream-enabled-database.md) to move the data associated with FileStream between different machines.  
 
 - Currently, this new enhancement does not support more than one SQL Server instance accessing the same database files in  Azure Storage at the same time. If ServerA is online with an active database file and if ServerB is accidentally started, and it also has a database which points to the same data file, the second server will fail to start the database with an error code **5120 Unable to open the physical file "%.\*ls". Operating system error %d: "%ls"**.  

docs/relational-databases/views/create-indexed-views.md

@@ -153,8 +153,8 @@ Indexes on tables and views can be disabled. When a clustered index on a table i
 
 To create the view, a user needs to hold the **CREATE VIEW** permission in the database and **ALTER** permission on the schema in which the view is being created. If the base table resides within a different schema, the **REFERENCES** permission on the table is required as a minimum. If the User creating the Index differs from the Users who created the View, for the Index creation alone the **ALTER**-permission on the View is required (covered by ALTER on the schema).
 
-    > [!NOTE]  
-    > Indexes can only be created on views which have the same owner as the referenced table or tables. This is also called an intact **ownership-chain** between the view and the table(s). Typically, when table and view reside within the same schema, the same schema-owner applies to all objects within the schema. But it is possible that individual objects have different explicit owners. The column **principal_id** in sys.tables contains a value if the owner is different from the schema-owner.
+> [!NOTE]  
+> Indexes can only be created on views which have the same owner as the referenced table or tables. This is also called an intact **ownership-chain** between the view and the table(s). Typically, when table and view reside within the same schema, the same schema-owner applies to all objects within the schema. Therefore its possible to create a view and not be the owner of the view. On the other hand is also possible that individual objects within a schema have different explicit owners. The column **principal_id** in sys.tables contains a value if the owner is different from the schema-owner.
 
 
 ## <a name="TsqlProcedure"></a> Using Transact-SQL