sqledge - edits

stevestein · stevestein · commit 91f98cd1f26d · 2020-05-07T15:01:43.000-07:00
diff --git a/articles/azure-sql-edge/backup-restore.md b/articles/azure-sql-edge/backup-restore.md
@@ -8,29 +8,29 @@ ms.topic: conceptual
 author: SQLSourabh
 ms.author: sourabha
 ms.reviewer: sstein
-ms.date: 04/28/2020
+ms.date: 05/19/2020
 ---
 
 # Backup and Restore databases in Azure SQL Edge Preview
 
-Azure SQL Edge is built on the latest versions of the Microsoft SQL Server Database Engine on Linux, providing similar backup and restore database capabilities as those available in SQL Server on Linux and SQL Server running in containers. Backup and restore component provides an essential safeguard for protecting data stored in your Azure SQL Edge databases. To minimize the risk of catastrophic data loss, its recommended that you back up your databases periodically to preserve modifications to your data on a regular basis. A well-planned backup and restore strategy helps protect databases against data loss caused by a variety of failures. Test your strategy by restoring a set of backups and then recovering your database to prepare you to respond effectively to a disaster.
+Azure SQL Edge is built on the latest versions of the Microsoft SQL Server Database Engine on Linux, providing similar backup and restore database capabilities as those available in SQL Server on Linux and SQL Server running in containers. Backup and restore component provides an essential safeguard for protecting data stored in your Azure SQL Edge databases. To minimize the risk of catastrophic data loss, it's recommended that you back up your databases periodically to preserve modifications to your data on a regular basis. A well-planned backup and restore strategy helps protect databases against data loss caused by a variety of failures. Test your strategy by restoring a set of backups and then recovering your database to prepare you to respond effectively to a disaster.
 
-To read more about why backups are important, please refer [Back Up and Restore of SQL Server Databases](https://docs.microsoft.com/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases?view=sql-server-ver15).
+To read more about why backups are important, see [Back Up and Restore of SQL Server Databases](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases/).
 
-Azure SQL Edge supports backing up and restoring from both local storage or from Azure blobs. For more information on backup to and restore from Azure Blob Storage, refer [SQL Server Backup and Restore with Microsoft Azure Blob Storage Service](https://docs.microsoft.com/sql/relational-databases/backup-restore/sql-server-backup-and-restore-with-microsoft-azure-blob-storage-service?view=sql-server-ver15) and [SQL Server Backup to URL](https://docs.microsoft.com/sql/relational-databases/backup-restore/sql-server-backup-to-url?view=sql-server-ver15).
+Azure SQL Edge supports backup to and restore from both local storage or from Azure blobs. For more information on backup to and restore from Azure Blob Storage, refer [SQL Server Backup and Restore with Microsoft Azure Blob Storage Service](/sql/relational-databases/backup-restore/sql-server-backup-and-restore-with-microsoft-azure-blob-storage-service/) and [SQL Server Backup to URL](/sql/relational-databases/backup-restore/sql-server-backup-to-url).
 
 ## Backing up a database in Azure SQL Edge
 
-Azure SQL Edge supports the same backup types as supported by SQL Server. For a complete list of the backup types supported in SQL Server, refer [Backup Overview](https://docs.microsoft.com/sql/relational-databases/backup-restore/backup-overview-sql-server?view=sql-server-ver15).
+Azure SQL Edge supports the same backup types as supported by SQL Server. For a complete list of the backup types supported in SQL Server, refer [Backup Overview](/sql/relational-databases/backup-restore/backup-overview-sql-server/).
 
 > [!IMPORTANT] 
-> Databases created in Azure SQL Edge use simple recovery model by default. As such log backups cannot be performed on these databases. If there is a need to perform log backups on these databases, an administrator would need to change the database recovery model to full recovery model. For a complete list of recovery models supported by SQL Server, refer [Recovery Model Overview](https://docs.microsoft.com/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver15#RMov).
+> Databases created in Azure SQL Edge use simple recovery model by default. As such log backups cannot be performed on these databases. If there is a need to perform log backups on these databases, an administrator would need to change the database recovery model to full recovery model. For a complete list of recovery models supported by SQL Server, refer [Recovery Model Overview](/sql/relational-databases/backup-restore/recovery-models-sql-server#RMov).
 
 ### Backup to local disk
 
-In the example provided below, BACKUP DATABASE Transact-SQL command to create a database backup in the container. For the purpose of this example, a new folder called "backup" is created to store the backup files.
+In the example provided below, BACKUP DATABASE Transact-SQL command is used to create a database backup in the container. For the purpose of this example, a new folder called "backup" is created to store the backup files.
 
-1. Create a folder to for the backups. This command needs to be executed on the host where your Azure SQL Edge container is running. In the command below replace **<AzureSQLEdge_Container_Name>** with the name of Azure SQL Edge container in your deployment.
+1. Create a folder for the backups. This command needs to be executed on the host where your Azure SQL Edge container is running. In the command below replace **<AzureSQLEdge_Container_Name>** with the name of Azure SQL Edge container in your deployment.
 
     ```bash
     sudo docker exec -it <AzureSQLEdge_Container_Name> mkdir /var/opt/mssql/backup
@@ -46,7 +46,7 @@ In the example provided below, BACKUP DATABASE Transact-SQL command to create a
     GO
     ```
 
-3. After you run the command and if the backup of the database is successful, you'll messages similar to the following in the results section of SSMS or ADS.
+3. After you run the command and if the backup of the database is successful, you'll see messages similar to the following in the results section of SSMS or ADS.
 
     ```txt
     10 percent processed.
@@ -172,4 +172,3 @@ STATS = 10;
 ```
 
 
-
diff --git a/articles/azure-sql-edge/stream-data.md b/articles/azure-sql-edge/stream-data.md
@@ -8,54 +8,61 @@ ms.topic: conceptual
 author: SQLSourabh
 ms.author: sourabha
 ms.reviewer: sstein
-ms.date: 04/28/2020
+ms.date: 05/19/2020
 ---
 
 # Data streaming in Azure SQL Edge Preview
 
-Azure SQL Edge Preview introduces support for a new feature, **T-SQL Streaming**, which provides real-time data streaming, analytics, and event-processing to analyze and process high volumes of fast streaming data from multiple sources simultaneously. *T-SQL Streaming* is built using the same high performance streaming engine that powers [Azure Stream Analytics](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-introduction) in Microsoft Azure, and supports the same set of capabilities offered by Azure Stream Analytics running on the edge.
+Azure SQL Edge Preview provides two different options to implement data streaming. 
 
-> [!NOTE]
-> Azure SQL Edge is currently in Preview, which means the T-SQL Streaming feature is also under preview and should NOT be used in production or pre-production environments.
+1. Deploying Azure Streaming Analytics Edge jobs created in Azure. For more information on how to deploy Azure Streaming Analytics Edge jobs in Azure SQL Edge refer [Deploy Azure Stream Analytics Jobs](stream-analytics.md).
+2. Using the new **T-SQL Streaming** feature to create streaming jobs in SQL Edge, without the need to configure streaming jobs in Azure. 
+
+While its possible to use both options to implement data streaming in SQL Edge, it is highly recommended to use only one. When using both, there may be possible race conditions which impact the functioning of the data streaming operations.
+
+The rest of this document refers to the new feature, **T-SQL Streaming**, which provides real-time data streaming, analytics, and event-processing to analyze and process high volumes of fast streaming data from multiple sources simultaneously. *T-SQL Streaming* is built using the same high performance streaming engine that powers [Azure Stream Analytics](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-introduction) in Microsoft Azure, and supports a similar set of capabilities offered by Azure Stream Analytics running on the edge.
 
-As with Azure Stream Analytics, T-SQL Streaming enables recognition of patterns and relationships in information extracted from a number of IoT input sources including devices, sensors, and applications. These patterns can be used to trigger actions and initiate workflows such as creating alerts, feeding information to a reporting or visualization solution, or storing the data for later usage. The following scenarios are examples of when you can use T-SQL Streaming
+As with Azure Stream Analytics, T-SQL Streaming enables recognition of patterns and relationships in information extracted from a number of IoT input sources including devices, sensors, and applications. These patterns can be used to trigger actions and initiate workflows such as creating alerts, feeding information to a reporting or visualization solution, or storing the data for later use. 
 
-* Analyze real-time telemetry streams from IoT devices
+The following scenarios are examples of when you can use T-SQL Streaming:
+
+* Analyze real-time telemetry streams from IoT devices.
 * Real-time Analytics of data generated from autonomous and driverless vehicles.
-* Remote monitoring and predictive maintenance of high value industrial or manufacturing assets
-* Anomaly detection and/or pattern recognition of IoT sensor readings in an agriculture or an energy farm
+* Remote monitoring and predictive maintenance of high value industrial or manufacturing assets.
+* Anomaly detection and/or pattern recognition of IoT sensor readings in an agriculture or an energy farm.
 
 ## How does T-SQL Streaming work?
 
-T-SQL Streaming works in exactly the same manner as [Azure Stream Analytics](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-introduction#how-does-stream-analytics-work), i.e. it uses the concept of streaming jobs for processing of real-time data streaming. A stream analytics job, consists of
+T-SQL Streaming works in exactly the same manner as [Azure Stream Analytics](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-introduction#how-does-stream-analytics-work), for example, it uses the concept of streaming jobs for processing of real-time data streaming. 
+
+A stream analytics job, consists of:
 
-- Stream Input - A Stream input defines the connections to a data source to read the data stream from. Azure SQL Edge, currently supports the following stream input types
-    * Edge Hub
-    * Kafka - Support for Kafka inputs is currently only available on Intel/AMD64 versions of Azure SQL Edge.
+- Stream Input - A Stream input defines the connections to a data source to read the data stream from. Azure SQL Edge currently supports the following stream input types:
+    - Edge Hub
+    - Kafka - Support for Kafka inputs is currently only available on Intel/AMD64 versions of Azure SQL Edge.
 
 - Stream Output - A Stream output defines the connections to a data source to write the data stream to. Azure SQL Edge currently supports the following stream output types
-    * Edge Hub
-    * SQL - The SQL output can be a local database within the SQL Edge instance or a remote SQL Server or Azure SQL Database. 
-    * Azure Blob Storage
+    - Edge Hub
+    - SQL - The SQL output can be a local database within the SQL Edge instance or a remote SQL Server or Azure SQL Database. 
+    - Azure Blob Storage
 
-- Stream Query - The stream query defines the transformations, aggregations, filters, sorting, and joins that needs to be applied to the input stream before it's written to the stream output. The stream query is based on the same query language used by Azure Stream Analytics. For more information on Azure Stream Analytics query language, refer [Stream Analytics Query Language](https://docs.microsoft.com/stream-analytics-query/stream-analytics-query-language-reference?).
+- Stream Query - The stream query defines the transformation, aggregations, filter, sorting, and joins that needs to be applied to the input stream before it's written to the stream output. The stream query is based on the same query language used by Azure Stream Analytics. For more information on Azure Stream Analytics query language, refer [Stream Analytics Query Language](https://docs.microsoft.com/stream-analytics-query/stream-analytics-query-language-reference?).
 
 > [!IMPORTANT]
 > T-SQL Streaming, unlike Azure Stream Analytics, currently does not support [using reference data for lookups](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-use-reference-data) or [using UDF's and UDA's in stream job](https://docs.microsoft.com/azure/stream-analytics/streaming-technologies#you-want-to-write-udfs-udas-and-custom-deserializers-in-a-language-other-than-javascript-or-c).
 
 > [!NOTE]
-> T-SQL Streaming only supports a subset of language surface area supported by Azure Stream Analytics. For more information on Azure Stream Analytics query language, refer [Stream Analytics Query Language](https://docs.microsoft.com/stream-analytics-query/stream-analytics-query-language-reference?).
+> T-SQL Streaming only supports a subset of the language surface area supported by Azure Stream Analytics. For more information on Azure Stream Analytics query language, see [Stream Analytics Query Language](https://docs.microsoft.com/stream-analytics-query/stream-analytics-query-language-reference?).
 
 ## Limitations and restrictions
 
-The following limitations and restrictions apply to SQL Streaming. 
+The following limitations and restrictions apply to T-SQL Streaming. 
 
-- Only one streaming job can be active at any give time. Users will have to stop an already executing job before starting another job.
+- Only one streaming job can be active at any give time. Jobs that are already executing must be stopped before starting another job.
 - Each streaming job execution is single threaded. If the streaming job contains multiple queries, each query will be evaluated in serial order.
 
 ## Next steps
 
 - [Create a Stream Analytics job in Azure SQL Edge Preview](create-stream-analytics-job.md)
-- [Start, Stop, Drop a stream analytics job in Azure SQL Edge Preview](overview.md)
-- [Viewing metadata associated with stream jobs in Azure SQL Edge Preview](overview.md)
-- [Create External Stream](overview.md)
+- [Viewing metadata associated with stream jobs in Azure SQL Edge Preview](streaming-catalog-views.md)
+- [Create External Stream](create-external-stream-transact-sql.md)
