From 94fc28f166fb4ca4beb68ef3bdc23510fe5f4ebb Mon Sep 17 00:00:00 2001 From: ThePiranha Date: Sun, 16 Dec 2018 17:09:44 +0600 Subject: [PATCH 1/4] added missing words in sentence --- docs/framework/data/adonet/sql/authentication-in-sql-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/data/adonet/sql/authentication-in-sql-server.md b/docs/framework/data/adonet/sql/authentication-in-sql-server.md index 25310bf84ddef..972496d5cc418 100644 --- a/docs/framework/data/adonet/sql/authentication-in-sql-server.md +++ b/docs/framework/data/adonet/sql/authentication-in-sql-server.md @@ -13,7 +13,7 @@ SQL Server supports two authentication modes, Windows authentication mode and mi > [!IMPORTANT] > We recommend using Windows authentication wherever possible. Windows authentication uses a series of encrypted messages to authenticate users in SQL Server. When SQL Server logins are used, SQL Server login names and encrypted passwords are passed across the network, which makes them less secure. - With Windows authentication, users are already logged onto Windows and do not have to log on separately to SQL Server. The following `SqlConnection.ConnectionString` specifies Windows authentication without requiring the a user name or password. + With Windows authentication, users are already logged onto Windows and do not have to log on separately to SQL Server. The following `SqlConnection.ConnectionString` specifies Windows authentication without requiring the users providing a user name or password. ``` "Server=MSSQL1;Database=AdventureWorks;Integrated Security=true; From d921a0ba7475b499f4d8849b9de02e744c04ec0f Mon Sep 17 00:00:00 2001 From: ThePiranha Date: Sun, 16 Dec 2018 18:50:48 +0600 Subject: [PATCH 2/4] Fixed spelling significant --- docs/framework/data/adonet/dataview-performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/data/adonet/dataview-performance.md b/docs/framework/data/adonet/dataview-performance.md index 2ab147dabb243..4892125d26039 100644 --- a/docs/framework/data/adonet/dataview-performance.md +++ b/docs/framework/data/adonet/dataview-performance.md @@ -10,7 +10,7 @@ ms.assetid: 90820e49-9d46-41f6-9a3d-6c0741bbd8eb This topic discusses the performance benefits of using the and methods of the class, and of caching a in a Web application. ## Find and FindRows - constructs an index. An index contains keys built from one or more columns in the table or view. These keys are stored in a structure that enables the to find the row or rows associated with the key values quickly and efficiently. Operations that use the index, such as filtering and sorting, see signifcant performance increases. The index for a is built both when the is created and when any of the sorting or filtering information is modified. Creating a and then setting the sorting or filtering information later causes the index to be built at least twice: once when the is created, and again when any of the sort or filter properties are modified. For more information about filtering and sorting with , see [Filtering with DataView](../../../../docs/framework/data/adonet/filtering-with-dataview-linq-to-dataset.md) and [Sorting with DataView](../../../../docs/framework/data/adonet/sorting-with-dataview-linq-to-dataset.md). + constructs an index. An index contains keys built from one or more columns in the table or view. These keys are stored in a structure that enables the to find the row or rows associated with the key values quickly and efficiently. Operations that use the index, such as filtering and sorting, see significant performance increases. The index for a is built both when the is created and when any of the sorting or filtering information is modified. Creating a and then setting the sorting or filtering information later causes the index to be built at least twice: once when the is created, and again when any of the sort or filter properties are modified. For more information about filtering and sorting with , see [Filtering with DataView](../../../../docs/framework/data/adonet/filtering-with-dataview-linq-to-dataset.md) and [Sorting with DataView](../../../../docs/framework/data/adonet/sorting-with-dataview-linq-to-dataset.md). If you want to return the results of a particular query on the data, as opposed to providing a dynamic view of a subset of the data, you can use the or methods of the , rather than setting the property. The property is best used in a data-bound application where a bound control displays filtered results. Setting the property rebuilds the index for the data, adding overhead to your application and decreasing performance. The and methods use the current index without requiring the index to be rebuilt. If you are going to call or only once, then you should use the existing . If you are going to call or multiple times, you should create a new to rebuild the index on the column you want to search on, and then call the or methods. For more information about the and methods, see [Finding Rows](../../../../docs/framework/data/adonet/dataset-datatable-dataview/finding-rows.md). From 36ea5ad9620fe3e64adf8c3a62ad55f35791d7d1 Mon Sep 17 00:00:00 2001 From: ThePiranha Date: Sun, 16 Dec 2018 20:16:35 +0600 Subject: [PATCH 3/4] removed double full stop --- docs/framework/data/adonet/sqlclient-streaming-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/data/adonet/sqlclient-streaming-support.md b/docs/framework/data/adonet/sqlclient-streaming-support.md index 7d07af8059bff..227fdb9b62c42 100644 --- a/docs/framework/data/adonet/sqlclient-streaming-support.md +++ b/docs/framework/data/adonet/sqlclient-streaming-support.md @@ -320,7 +320,7 @@ GO - Using the new asynchronous feature and the await keyword to transfer a large BLOB. -- Cancelling the transfer of a large BLOB.. +- Cancelling the transfer of a large BLOB. - Streaming from one SQL Server to another using the new asynchronous feature. From c8c918d57c8db4f67cc50aba240d88131d52f8b3 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Mon, 17 Dec 2018 11:29:28 +0600 Subject: [PATCH 4/4] Update docs/framework/data/adonet/sql/authentication-in-sql-server.md changes updated on feedback Co-Authored-By: ThePiranha --- docs/framework/data/adonet/sql/authentication-in-sql-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/data/adonet/sql/authentication-in-sql-server.md b/docs/framework/data/adonet/sql/authentication-in-sql-server.md index 972496d5cc418..1a06606b54e89 100644 --- a/docs/framework/data/adonet/sql/authentication-in-sql-server.md +++ b/docs/framework/data/adonet/sql/authentication-in-sql-server.md @@ -13,7 +13,7 @@ SQL Server supports two authentication modes, Windows authentication mode and mi > [!IMPORTANT] > We recommend using Windows authentication wherever possible. Windows authentication uses a series of encrypted messages to authenticate users in SQL Server. When SQL Server logins are used, SQL Server login names and encrypted passwords are passed across the network, which makes them less secure. - With Windows authentication, users are already logged onto Windows and do not have to log on separately to SQL Server. The following `SqlConnection.ConnectionString` specifies Windows authentication without requiring the users providing a user name or password. + With Windows authentication, users are already logged onto Windows and do not have to log on separately to SQL Server. The following `SqlConnection.ConnectionString` specifies Windows authentication without requiring users to provide a user name or password. ``` "Server=MSSQL1;Database=AdventureWorks;Integrated Security=true;