MicrosoftDocs · fenxu · Jul 10, 2019 · Jul 1, 2019 · Jul 1, 2019 · Jul 2, 2019
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -75,6 +75,9 @@
             "redirect_url": "/sql/linux/sql-server-linux-active-directory-authentication",
             "redirect_document_id": false
         },
+
+
+
         {
             "source_path": "docs/toc/redirectfrom-reference-10.md",
             "redirect_url": "/sql/sql-server/applies-to-includes",
@@ -85,6 +88,26 @@
             "redirect_url": "/sql/relational-databases/databases/databases",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/relational-databases/tables/create-edge-constraints.md",
+            "redirect_url": "/sql/relational-databases/tables/graph-edge-constraints",
+            "redirect_document_id": false 
+        },
+        {
+            "source_path": "docs/relational-databases/tables/delete-edge-constraint.md",
+            "redirect_url": "/sql/relational-databases/tables/graph-edge-constraints",
+            "redirect_document_id": false 
+        },
+        {
+            "source_path": "docs/relational-databases/tables/modify-edge-constraint.md",
+            "redirect_url": "/sql/relational-databases/tables/graph-edge-constraints",
+            "redirect_document_id": false 
+        },
+        {
+            "source_path": "docs/relational-databases/tables/view-edge-constraint-properties.md",
+            "redirect_url": "/sql/relational-databases/tables/graph-edge-constraints",
+            "redirect_document_id": false 
+        },       
         {
             "source_path": "docs/relational-databases/polybase/get-started-with-polybase.md",
             "redirect_url": "/sql/relational-databases/polybase/polybase-guide",

diff --git a/docs/2014/2014-toc/case-study-building-an-enterprise-ecosystem.md b/docs/2014/2014-toc/case-study-building-an-enterprise-ecosystem.md
@@ -20,13 +20,13 @@ How to understand the specifics involved while leveraging transactional replicat
 
  This content is suitable for developers, architects, and database administrators. It is assumed that readers of this white paper have basic knowledge of SQL Server 2008, 2012, or 2014 as well as SQL Server administration experience.  
 
- **Writer:**Prabhakaran Sethuraman (PRAB), Microsoft  
+ **Writer:** Prabhakaran Sethuraman (PRAB), Microsoft  
 
- **Technical Reviewers:**Prabhakaran Sethuraman (PRAB), Microsoft; Santosh Padhy, Microsoft; Pavel Majstrov, Microsoft; Karthik Sankaranarayanan, Microsoft; Jon Acone, Microsoft; David Stahlkopf, Microsoft;Kent Oldenburger, Microsoft; Mandi Ohlinger, Microsoft; Jason Roth, Microsoft  
+ **Technical Reviewers:** Prabhakaran Sethuraman (PRAB), Microsoft; Santosh Padhy, Microsoft; Pavel Majstrov, Microsoft; Karthik Sankaranarayanan, Microsoft; Jon Acone, Microsoft; David Stahlkopf, Microsoft;Kent Oldenburger, Microsoft; Mandi Ohlinger, Microsoft; Jason Roth, Microsoft  
 
- **Published:**October 2015  
+ **Published:** October 2015  
 
- **Applies to:**SQL Server 2008, SQL Server 2012, and SQL Server 2014  
+ **Applies to:** SQL Server 2008, SQL Server 2012, and SQL Server 2014  
 
  To review the document, please download the  
         [Case Study: Building an Enterprise Ecosystem with Microsoft Dynamics ERP and SQL Server 2014 Replication for Scalability and Performance](https://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/A%20Case%20Study%20Using%20Replication%20to%20Build%20an%20Enterprise%20Ecosystem%20in%20Microsoft%20Dynamics%20ERP%20for%20Scalability%20and%20Performance.docx) Word document.  

diff --git a/...-engine/availability-groups/windows/always-on-client-connectivity-sql-server.md b/...-engine/availability-groups/windows/always-on-client-connectivity-sql-server.md
@@ -31,8 +31,8 @@ manager: craigg
 |------------|----------------------------|------------------------|------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------------|  
 |SQL Native Client 11.0 ODBC|Yes|Yes|Yes|Yes|Yes|  
 |SQL Native Client 11.0 OLEDB|No|Yes|Yes|No|No|  
-|ADO.NET with .NET Framework 4.0 with connectivity patch**<sup>*</sup>**|Yes|Yes|Yes|Yes|Yes|  
-|ADO.NET with .NET Framework 3.5 SP1 with connectivity patch **<sup>**</sup>**|Yes|Yes|Yes|Yes|Yes|  
+|ADO.NET with .NET Framework 4.0 with connectivity patch**<sup>*</sup>** |Yes|Yes|Yes|Yes|Yes|  
+|ADO.NET with .NET Framework 3.5 SP1 with connectivity patch **<sup>**</sup>** |Yes|Yes|Yes|Yes|Yes|  
 |Microsoft JDBC driver 4.0 for SQL Server|Yes|Yes|Yes|Yes|Yes|  
 
  **<sup>*</sup>**  Download the connectivity patch for ADO .NET with .NET Framework 4.0: [https://support.microsoft.com/kb/2600211](https://support.microsoft.com/kb/2600211).  

diff --git a/...g/add-a-database-mirroring-witness-using-windows-authentication-transact-sql.md b/...g/add-a-database-mirroring-witness-using-windows-authentication-transact-sql.md
@@ -27,7 +27,7 @@ manager: craigg
 
 ### To establish a witness  
 
-1.  On the witness server instance, ensure that an endpoint exists for database mirroring. Regardless of the number of mirroring session to be supported, the server instance must have only one database mirroring endpoint. If you intend to use this server instance exclusively as a witness in database mirroring sessions, assign the role of witness to the endpoint (ROLE**=**WITNESS). If you intend to use this server instance as a partner in one or more other database mirroring sessions, assign the role of the endpoint as ALL.  
+1.  On the witness server instance, ensure that an endpoint exists for database mirroring. Regardless of the number of mirroring session to be supported, the server instance must have only one database mirroring endpoint. If you intend to use this server instance exclusively as a witness in database mirroring sessions, assign the role of witness to the endpoint (ROLE **=** WITNESS). If you intend to use this server instance as a partner in one or more other database mirroring sessions, assign the role of the endpoint as ALL.  
 
      To execute a SET WITNESS statement, the database mirroring session must already be started (between the partners), and the STATE of the endpoint of the witness must be set to STARTED.  
 
@@ -46,7 +46,7 @@ manager: craigg
 
 3.  Connect to the principal server and issue the following statement:  
 
-     ALTER DATABASE *<database_name>* SET WITNESS **=**_<server_network_address>_  
+     ALTER DATABASE *<database_name>* SET WITNESS **=** _<server_network_address>_  
 
      where *<database_name>* is the name of the database to be mirrored (this name is the same on both partners), and *<server_network_address>* is the server network address of the witness server instance.  
 

diff --git a/...14/relational-databases/errors-events/mssqlserver-1505-database-engine-error.md b/...14/relational-databases/errors-events/mssqlserver-1505-database-engine-error.md
@@ -24,7 +24,7 @@ manager: craigg
 |Event Source|MSSQLSERVER|  
 |Component|SQLEngine|  
 |Symbolic Name|DUP_KEY|  
-|Message Text|CREATE UNIQUE INDEX terminated because a duplicate key was found for object name '%.*ls' and index name '%.\*ls'.  The duplicate key value is %ls.|  
+|Message Text|CREATE UNIQUE INDEX terminated because a duplicate key was found for object name '%.\*ls' and index name '%.\*ls'.  The duplicate key value is %ls.|  
 
 ## Explanation  
  This error occurs when you attempt to create a unique index and more than one row in the table contains the specified duplicate value. A unique index is created when you create an index and specify the UNIQUE keyword, or when you create a UNIQUE constraint. The table cannot contain any rows that have duplicate values in the columns defined in the index or constraint.  
@@ -44,7 +44,7 @@ manager: craigg
 
  Error message 1505 returns the first row that violates the uniqueness constraint. There may be other duplicate rows in the table. To find all duplicate rows, query the specified table and use the GROUP BY and HAVING clauses to report the duplicate rows. For example, the following query returns the rows in the **Employee** table that have duplicate first and last names.  
 
- SELECT LastName, FirstName, count(*) FROM dbo.Employee GROUP BY LastName, FirstName HAVING count(\*) > 1;  
+ SELECT LastName, FirstName, count(\*) FROM dbo.Employee GROUP BY LastName, FirstName HAVING count(\*) > 1;  
 
 ## User Action  
  Consider the following solutions.  

diff --git a/...atabases/policy-based-management/lesson-1-1-create-the-off-by-default-policy.md b/...atabases/policy-based-management/lesson-1-1-create-the-off-by-default-policy.md
@@ -22,7 +22,7 @@ manager: craigg
 
 3.  In the **Facet** box, confirm that **Surface Area Configuration** facet is selected.  
 
-4.  In the **Expression** area, in the **Field** box, select **@DatabaseMailEnabled**, in the **Operator** box select **=**, and in the **Value** select **False**.  
+4.  In the **Expression** area, in the **Field** box, select **\@DatabaseMailEnabled**, in the **Operator** box select **=**, and in the **Value** select **False**.  
 
 5.  On the **Description** page, type a description of the condition, and then click **OK** to create the condition.  
 

diff --git a/...-databases/policy-based-management/lesson-2-1-create-the-finance-name-policy.md b/...-databases/policy-based-management/lesson-2-1-create-the-finance-name-policy.md
@@ -33,7 +33,7 @@ manager: craigg
 
 3.  In the **Facet** list, select **Multipart Name**.  
 
-4.  In the **Expression** area, in the **Field** box, select **@Name**; in the **Operator** box, select **Like**; and in the **Value** box, type **'fintbl%'** to force all table names to start with the letters **fintbl**.  
+4.  In the **Expression** area, in the **Field** box, select **\@Name**; in the **Operator** box, select **Like**; and in the **Value** box, type **'fintbl%'** to force all table names to start with the letters **fintbl**.  
 
 5.  On the **Description** page, type **Finance table names must begin with fintbl**, and then click **OK** to create the condition.  
 
@@ -51,7 +51,7 @@ manager: craigg
 
 6.  In the **Create New Condition** dialog box, in the **Name** box, type **Finance Database**.  
 
-7.  In the **Expression** box, complete the expression to include **@Name = 'Finance'**, and then click **OK** to close the condition page.  
+7.  In the **Expression** box, complete the expression to include **\@Name = 'Finance'**, and then click **OK** to close the condition page.  
 
     > [!NOTE]  
     >  You might have to tab out of the **Value** box to enable the **OK** button.  

diff --git a/...ion/administration/configure-the-transaction-set-job-for-an-oracle-publisher.md b/...ion/administration/configure-the-transaction-set-job-for-an-oracle-publisher.md
@@ -23,27 +23,27 @@ manager: craigg
 
 1.  At the Oracle Publisher, set the **job_queue_processes** initialization parameter to a sufficient value to allow the Xactset job run. For more information about this parameter, see the database documentation for the Oracle Publisher.  
 
-2.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**, a value of `xactsetbatching` for **@propertyname**, and a value of `enabled` for **@propertyvalue**.  
+2.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**, a value of `xactsetbatching` for **\@propertyname**, and a value of `enabled` for **\@propertyvalue**.  
 
-3.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**, a value of `xactsetjobinterval` for **@propertyname**, and the job interval, in minutes, for **@propertyvalue**.  
+3.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**, a value of `xactsetjobinterval` for **\@propertyname**, and the job interval, in minutes, for **\@propertyvalue**.  
 
-4.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**, a value of `xactsetjob` for **@propertyname**, and a value of `enabled` for **@propertyvalue**.  
+4.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**, a value of `xactsetjob` for **\@propertyname**, and a value of `enabled` for **\@propertyvalue**.  
 
 ### To configure the transaction set job  
 
-1.  (Optional) At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**. This returns properties of the **Xactset** job at the Publisher.  
+1.  (Optional) At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**. This returns properties of the **Xactset** job at the Publisher.  
 
-2.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**, the name of the Xactset job property being set for **@propertyname**, and new setting for **@propertyvalue**.  
+2.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**, the name of the Xactset job property being set for **\@propertyname**, and new setting for **\@propertyvalue**.  
 
 3.  (Optional) Repeat step 2 for each Xactset job property being set. When changing the `xactsetjobinterval` property, you must restart the job on the Oracle Publisher for the new interval to take effect.  
 
 ### To view properties of the transaction set job  
 
-1.  At the Distributor, execute [sp_helpxactsetjob](/sql/relational-databases/system-stored-procedures/sp-helpxactsetjob-transact-sql). Specify the name of the Oracle Publisher for **@publisher**.  
+1.  At the Distributor, execute [sp_helpxactsetjob](/sql/relational-databases/system-stored-procedures/sp-helpxactsetjob-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**.  
 
 ### To disable the transaction set job  
 
-1.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **@publisher**, a value of `xactsetjob` for **@propertyname**, and a value of `disabled` for **@propertyvalue**.  
+1.  At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql). Specify the name of the Oracle Publisher for **\@publisher**, a value of `xactsetjob` for **\@propertyname**, and a value of `disabled` for **\@propertyvalue**.  
 
 ## Example  
  The following example enables the `Xactset` job and sets an interval of three minutes between runs.  

diff --git a/...tion/administration/enable-coordinated-backups-for-transactional-replication.md b/...tion/administration/enable-coordinated-backups-for-transactional-replication.md
@@ -26,7 +26,7 @@ manager: craigg
 
 1.  At the Publisher, use the [DATABASEPROPERTYEX &#40;Transact-SQL&#41;](/sql/t-sql/functions/databasepropertyex-transact-sql) function to return the **IsSyncWithBackup** property of the publication database. If the function returns **1**, coordinated backups are already enabled for the published database.  
 
-2.  If the function in step 1 returns **0**, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql) at the Publisher on the publication database. Specify a value of **sync with backup** for **@optname**, and **true** for **@value**.  
+2.  If the function in step 1 returns **0**, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql) at the Publisher on the publication database. Specify a value of **sync with backup** for **\@optname**, and **true** for **\@value**.  
 
     > [!NOTE]  
     >  If you change the **sync with backup** option to **false**, the truncation point of the publication database will be updated after the Log Reader Agent runs, or after an interval if the Log Reader Agent is running continuously. The maximum interval is controlled by the **-MessageInterval** agent parameter (which has a default of 30 seconds).  
@@ -35,10 +35,10 @@ manager: craigg
 
 1.  At the Distributor, use the [DATABASEPROPERTYEX &#40;Transact-SQL&#41;](/sql/t-sql/functions/databasepropertyex-transact-sql) function to return the **IsSyncWithBackup** property of the distribution database. If the function returns **1**, coordinated backups are already enabled for the distribution database.  
 
-2.  If the function in step 1 returns **0**, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql) at the Distributor on the distribution database. Specify a value of **sync with backup** for **@optname** and **true** for **@value**.  
+2.  If the function in step 1 returns **0**, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql) at the Distributor on the distribution database. Specify a value of **sync with backup** for **\@optname** and **true** for **\@value**.  
 
 ### To disable coordinated backups  
 
-1.  At either the Publisher on the publication database or at the Distributor on the distribution database, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql). Specify a value of **sync with backup** for **@optname** and **false** for **@value**.  
+1.  At either the Publisher on the publication database or at the Distributor on the distribution database, execute [sp_replicationdboption &#40;Transact-SQL&#41;](/sql/relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql). Specify a value of **sync with backup** for **\@optname** and **false** for **\@value**.