diff --git a/doc/snippets/Microsoft.Data.Sql/SqlDataSourceEnumerator.xml b/doc/snippets/Microsoft.Data.Sql/SqlDataSourceEnumerator.xml index c06899ed01..57357e96e9 100644 --- a/doc/snippets/Microsoft.Data.Sql/SqlDataSourceEnumerator.xml +++ b/doc/snippets/Microsoft.Data.Sql/SqlDataSourceEnumerator.xml @@ -7,7 +7,7 @@ SQL Server makes it possible for applications to determine the existence of its instances within the current network. The class exposes this information to the application developer, providing a containing information about all the available servers. This returned table contains a list of server instances that matches the list provided when a user attempts to create a new connection, and on the Connection Properties dialog box, expands the drop-down list containing all the available servers. - + Enumerating Instances of SQL Server @@ -98,7 +98,7 @@ } - + Enumerating Instances of SQL Server @@ -179,7 +179,7 @@ } - + Enumerating Instances of SQL Server diff --git a/doc/snippets/Microsoft.Data.Sql/SqlNotificationRequest.xml b/doc/snippets/Microsoft.Data.Sql/SqlNotificationRequest.xml index 84c1a02c13..75f09d283b 100644 --- a/doc/snippets/Microsoft.Data.Sql/SqlNotificationRequest.xml +++ b/doc/snippets/Microsoft.Data.Sql/SqlNotificationRequest.xml @@ -7,7 +7,7 @@ This class provides low-level access to the query notification services exposed by SQL Server 2005. For most applications the class provides a simpler way of using query notifications. However, if you need fine control over when notifications occur, or you need to customize the message data returned as part of a notification, the class is the one to use. - + Using Query Notifications @@ -18,7 +18,7 @@ If the parameterless constructor is used to create a object, that instance must have its and properties initialized before assigning the object to a object's property. The default values used by the constructor are (Nothing in Visual Basic) for the , an empty string for the , and zero for the . - + Using Query Notifications @@ -44,7 +44,7 @@ The or parameter is longer than or the value in the parameter is less than zero. - + Using Query Notifications @@ -78,7 +78,7 @@ The value is longer than . - + Using Query Notifications @@ -95,7 +95,7 @@ The value is less than zero. - + Using Query Notifications @@ -112,7 +112,7 @@ The value is longer than . - + Using Query Notifications diff --git a/doc/snippets/Microsoft.Data.SqlClient.Server/SqlMetaData.xml b/doc/snippets/Microsoft.Data.SqlClient.Server/SqlMetaData.xml index 47b515b911..cbabfd8cb0 100644 --- a/doc/snippets/Microsoft.Data.SqlClient.Server/SqlMetaData.xml +++ b/doc/snippets/Microsoft.Data.SqlClient.Server/SqlMetaData.xml @@ -615,7 +615,7 @@ Initializes a new instance of the class with the specified column name, and default server. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -644,7 +644,7 @@ Initializes a new instance of the class with the specified column name, type, maximum length, and server default. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -676,7 +676,7 @@ Initializes a new instance of the class with the specified column name, type, precision, scale, and server default. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -931,7 +931,7 @@ Initializes a new instance of the class with the specified column name, type, user-defined type, SQL Server type, and server default. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -966,7 +966,7 @@ Initializes a new instance of the class with the specified column name, type, maximum length, locale, compare options, and server default. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -1001,7 +1001,7 @@ Initializes a new instance of the class with the specified column name, database name, owning schema, object name, and default server. This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -1045,7 +1045,7 @@ Initializes a new instance of the class with the specified column name, type, maximum length, precision, scale, locale ID, compare options, and user-defined type (UDT). This form of the constructor supports table-valued parameters by allowing you to specify if the column is unique in the table-valued parameter, the sort order for the column, and the ordinal of the sort column. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -1505,7 +1505,7 @@ This property can only be set in one of the constructors. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -1597,7 +1597,7 @@ This property can only be set in one of the constructors. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. @@ -1616,7 +1616,7 @@ This property can only be set in one of the constructors. - For more information, see Table-Valued Parameters. + For more information, see Table-Valued Parameters. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBatch.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBatch.xml index a961ce136c..6811f5735e 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBatch.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBatch.xml @@ -330,7 +330,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming, see Asynchronous Programming. + For more information about asynchronous programming, see Asynchronous Programming. This method stores in the task it returns all non-usage exceptions that the method's synchronous counterpart can throw. If an exception is stored into the returned task, that exception will be thrown when the task is awaited. Usage exceptions, such as , are still thrown synchronously. For the stored exceptions, see the exceptions thrown by . @@ -365,7 +365,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming, see Asynchronous Programming. + For more information about asynchronous programming, see Asynchronous Programming. If an exception is stored into the returned task, that exception will be thrown when the task is awaited. Usage exceptions, such as , are still thrown synchronously. @@ -375,7 +375,7 @@ An error occurred while executing the batch. - ADO.NET Overview + Overview of the SqlClient driver The cancellation token was canceled. This exception is stored into the returned task. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBatchCommand.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBatchCommand.xml index cfce5cfce9..2fe3166a6c 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBatchCommand.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBatchCommand.xml @@ -74,7 +74,7 @@ A collection of objects is used to create the . - The encryption setting. For more information, see Always Encrypted. + The encryption setting. For more information, see Always Encrypted. @@ -93,7 +93,7 @@ Not currently implemented. - The encryption setting. For more information, see Always Encrypted. + The encryption setting. For more information, see Always Encrypted. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml index 2e75dbbd62..082e28aee9 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml @@ -10,7 +10,7 @@ The following console application demonstrates how to load data using the class. In this example, a is used to copy data from the Production.Product table in the SQL Server AdventureWorks database to a similar table in the same database. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. using System; @@ -115,7 +115,7 @@ The following console application demonstrates how to bulk load data using a connection that is already open. In this example, a is used to copy data from the Production.Product table in the SQL Server AdventureWorks database to a similar table in the same database. This example is for demonstration purposes only. You would not use SqlBulkCopy to move data from one table to another in the same database in a production application. Note that the source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -225,12 +225,12 @@ If options include and the argument is not , an InvalidArgumentException is thrown. - For examples demonstrating how to use SqlBulkCopy in a transaction, see Transaction and Bulk Copy Operations. + For examples demonstrating how to use SqlBulkCopy in a transaction, see Transaction and Bulk Copy Operations. - + Performing Bulk Copy Operations - + Overview of the SqlClient driver @@ -254,7 +254,7 @@ The following console application demonstrates how to bulk load data by using a connection specified as a string. The connection is automatically closed when the instance is closed. In this example, the source data is first read from a SQL Server table to a instance. The source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -358,7 +358,7 @@ The following console application demonstrates how to perform a bulk load by using a connection specified as a string. An option is set to use the value in the identity column of the source table when you load the destination table. In this example, the source data is first read from a SQL Server table to a instance. The source table and destination table each include an Identity column. By default, a new value for the Identity column is generated in the destination table for each row added. In this example, an option is set when the connection is opened that forces the bulk load process to use the Identity values from the source table instead. To see how the option changes the way the bulk load works, run the sample with the dbo.BulkCopyDemoMatchingColumns table empty. All rows load from the source. Then run the sample again without emptying the table. An exception is thrown and the code writes a message to the console notifying you that rows weren't added because of primary key constraint violations. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -465,10 +465,10 @@ - The following console application demonstrates how to bulk load data in batches of 50 rows. For an example illustrating how works with a transaction, see Transaction and Bulk Copy Operations. + The following console application demonstrates how to bulk load data in batches of 50 rows. For an example illustrating how works with a transaction, see Transaction and Bulk Copy Operations. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -567,7 +567,7 @@ The following console application demonstrates how to modify the time-out to 60 seconds when bulk loading data. In this example, the source data is first read from a SQL Server table to a instance. The source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -667,7 +667,7 @@ The following example uses the same instance to add sales orders and their associated details to two destination tables. Because the AdventureWorks sales order tables are large, the sample reads only orders placed by a certain account number and bulk copies those orders and details to the destination tables. The method is used only after both bulk copy operations are complete. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -896,7 +896,7 @@ In this example, the connection is first used to read data from a SQL Server table to a instance. The source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1012,7 +1012,7 @@ In this example, the connection is first used to read data from a SQL Server table to a instance. Then a second connection is opened to bulk copy the data. Note that the source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1115,7 +1115,7 @@ Note that the settings of and are independent. Receipt of a event does not imply that any rows have been sent to the server or committed. - You cannot call or from this event. Doing this will cause an being thrown, and the object state will not change. If the user wants to cancel the operation from the event, the property of the can be used. (See Transaction and Bulk Copy Operations for examples that use the property.) + You cannot call or from this event. Doing this will cause an being thrown, and the object state will not change. If the user wants to cancel the operation from the event, the property of the can be used. (See Transaction and Bulk Copy Operations for examples that use the property.) No action, such as transaction activity, is supported in the connection during the execution of the bulk copy operation, and it is recommended that you not use the same connection used during the event. However, you can open a different connection. @@ -1129,7 +1129,7 @@ In this example, the connection is first used to read data from a SQL Server table to a instance. Note that the source data does not have to be located on SQL Server; you can use any data source that can be read to an or loaded to a . - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1267,7 +1267,7 @@ Call Dispose when you are finished using the . The Dispose method leaves the in an unusable state. After calling Dispose, you must release all references to the so the garbage collector can reclaim the memory that the was occupying. - For more information, see Cleaning Up Unmanaged Resources and Implementing a Dispose Method. + For more information, see Cleaning Up Unmanaged Resources and Implementing a Dispose Method. Always call Dispose before you release your last reference to the . Otherwise, the resources it is using will not be freed until the garbage collector calls the object's Finalize method. @@ -1311,7 +1311,7 @@ The following console application demonstrates how to bulk load data from a . The destination table is a table in the AdventureWorks database. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1420,7 +1420,7 @@ The following Console application demonstrates how to bulk load data from a . The destination table is a table in the AdventureWorks database. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. In this example, a is created at run time and is the source of the SqlBulkCopy operation. @@ -1545,10 +1545,10 @@ A did not specify a valid destination column name. - + Performing Bulk Copy Operations - + Overview of the SqlClient driver @@ -1584,7 +1584,7 @@ In this example, a is created at run time and three rows are added to it. Before the method is executed, one of the rows is edited. The method is called with a argument, so only the two unchanged rows are bulk copied to the destination. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. using System; @@ -1732,7 +1732,7 @@ In this example, a is created at run time. A single row is selected from the to copy to the destination table. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. using System; @@ -1868,7 +1868,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -1900,7 +1900,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -1929,7 +1929,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -1976,7 +1976,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2011,7 +2011,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2042,7 +2042,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2075,7 +2075,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2107,7 +2107,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2143,7 +2143,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMapping.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMapping.xml index edef794199..9ff6c6427d 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMapping.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMapping.xml @@ -24,7 +24,7 @@ sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, and each destination column is in the same ordinal position as its corresponding source column, the column names do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for usingSqlBulkCopyonly. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -130,7 +130,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -239,7 +239,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy based on the ordinal positions of the columns. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -353,7 +353,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -467,7 +467,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -580,7 +580,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -689,7 +689,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -805,7 +805,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -921,7 +921,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1037,7 +1037,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMappingCollection.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMappingCollection.xml index 3d867f3a24..b810a4ebbd 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMappingCollection.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnMappingCollection.xml @@ -23,7 +23,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. are added to the for the object to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -129,7 +129,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -248,7 +248,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy using the ordinal position of the source and destination columns. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -360,7 +360,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -472,7 +472,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. objects are used to create a column map for the bulk copy. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -584,7 +584,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. Although the number of columns in the destination matches the number of columns in the source, the column names and ordinal positions do not match. The code creates a object by specifying the column names. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -692,7 +692,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. Although not strictly necessary in this example (because the ordinal positions of the source and destination columns do match), the example defines column mappings for each bulk copy operation. The method must be used after the first bulk copy is performed and before the next bulk copy's column mappings are defined. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -935,7 +935,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. Although not strictly necessary in this example (because the ordinal positions of the source and destination columns do match), the example defines column mappings for each bulk copy operation. Both bulk copies include a mapping for the SalesOrderID, so rather than clearing the entire collection between bulk copy operations, the example removes all mappings except for the SalesOrderID mapping and then adds the appropriate mappings for the second bulk copy operation. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -1130,7 +1130,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. Although not strictly necessary in this example (because the ordinal positions of the source and destination columns do match), the example defines column mappings for each bulk copy operation. Both bulk copies include a mapping for the SalesOrderID, so rather than clearing the entire collection between bulk copy operations, the example removes all mappings except for the SalesOrderID mapping and then adds the appropriate mappings for the second bulk copy operation. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHint.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHint.xml index 3b205e171d..9a57501ce3 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHint.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHint.xml @@ -29,7 +29,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is used to define the sort order for the ProductNumber destination column. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -134,7 +134,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is used to define the sort order for the ProductNumber destination column. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -239,7 +239,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is used to define the sort order for the ProductNumber destination column. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -349,7 +349,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is used to define the sort order for the ProductNumber destination column. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHintCollection.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHintCollection.xml index 528a6a6065..da4d5ff534 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHintCollection.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyColumnOrderHintCollection.xml @@ -29,7 +29,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. s are added to the of the object to specify order hints for the bulk copy operation. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -133,7 +133,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is used to define the sort order for the ProductNumber destination column. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -246,7 +246,7 @@ The following example bulk copies data from a source table in the AdventureWorks sample database to a destination table in the same database. A SqlBulkCopyColumnOrderHint object is added to the by providing the destination column name and its sort order. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -353,7 +353,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. The example defines a column order hint for each bulk copy operation. The method must be used after the first bulk copy is performed and before the next bulk copy's order hint is defined. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -624,7 +624,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. The example defines a column order hint for the OrderDate column in the first bulk copy operation. The hint is removed before the second bulk copy operation. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. @@ -830,7 +830,7 @@ The following example performs two bulk copy operations. The first operation copies sales order header information, and the second copies sales order details. The example defines a column order hint for the OrderDate column in the first bulk copy operation. The hint is removed before the second bulk copy operation. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyOptions.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyOptions.xml index 50f149ee01..987bbd40c9 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyOptions.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopyOptions.xml @@ -17,7 +17,7 @@ To see how the option changes the way the bulk load works, run the sample with the dbo.BulkCopyDemoMatchingColumns table empty. All rows load from the source. Next, run the sample again without emptying the table. An exception is thrown, and the code writes a message to the console window notifying you that rows were not added because of primary key violations. - This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. + This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlClientPermission.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlClientPermission.xml index 0c7ba2ff03..02ada91280 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlClientPermission.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlClientPermission.xml @@ -37,7 +37,7 @@ Initializes a new instance of the class. - The enumeration takes precedence over the property. Therefore, if you set to , you must also set to None to prevent a user from making a connection using a blank password. For an example demonstrating how to use security demands, see Code Access Security and ADO.NET. + The enumeration takes precedence over the property. Therefore, if you set to , you must also set to None to prevent a user from making a connection using a blank password. For an example demonstrating how to use security demands, see Code Access Security and ADO.NET. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCertificateStoreProvider.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCertificateStoreProvider.xml index c7529fc744..bef463494c 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCertificateStoreProvider.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCertificateStoreProvider.xml @@ -2,7 +2,7 @@ - The implementation of the key store provider for Windows Certificate Store. This class enables using certificates stored in the Windows Certificate Store as column master keys. For details, see Always Encrypted. + The implementation of the key store provider for Windows Certificate Store. This class enables using certificates stored in the Windows Certificate Store as column master keys. For details, see Always Encrypted. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCngProvider.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCngProvider.xml index d4db77f1a3..b6dd7ffa5a 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCngProvider.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCngProvider.xml @@ -2,7 +2,7 @@ - The CMK Store provider implementation for using the Microsoft Cryptography API: Next Generation (CNG) with Always Encrypted. + The CMK Store provider implementation for using the Microsoft Cryptography API: Next Generation (CNG) with Always Encrypted. Enables storing Always Encrypted column master key keys in a store, such as a hardware security module (HSM), that supports the Microsoft Cryptography API: Next Generation (CNG). diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCspProvider.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCspProvider.xml index 21bddf73b2..975fd65722 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCspProvider.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionCspProvider.xml @@ -2,7 +2,7 @@ - The CMK Store provider implementation for using Microsoft CAPI based Cryptographic Service Providers (CSP) with Always Encrypted. + The CMK Store provider implementation for using Microsoft CAPI based Cryptographic Service Providers (CSP) with Always Encrypted. Enables storing Always Encrypted column master key keys in a store, such as a hardware security module (HSM), that supports the Microsoft CAPI based Cryptographic Service Providers (CSP). diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionKeyStoreProvider.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionKeyStoreProvider.xml index 8d57587c77..35be0d1817 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionKeyStoreProvider.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlColumnEncryptionKeyStoreProvider.xml @@ -2,7 +2,7 @@ - Base class for all key store providers. A custom provider must derive from this class and override its member functions and then register it using , or . For details see, Always Encrypted. + Base class for all key store providers. A custom provider must derive from this class and override its member functions and then register it using , or . For details see, Always Encrypted. @@ -62,7 +62,7 @@ To ensure that the method doesn't break applications that rely on an old API, it throws a exception by default. - The method will be used by client tools that generate Column Master Keys (CMK) for customers. must be implemented by the corresponding key store providers that wish to use enclaves with Always Encrypted. + The method will be used by client tools that generate Column Master Keys (CMK) for customers. must be implemented by the corresponding key store providers that wish to use enclaves with Always Encrypted. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlCommand.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlCommand.xml index 5a319a119f..73a21bd60b 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlCommand.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlCommand.xml @@ -724,7 +724,7 @@ The in which the executes. - The encryption setting. For more information, see Always Encrypted. + The encryption setting. For more information, see Always Encrypted. Initializes a new instance of the class with specified command text, connection, transaction, and encryption setting. @@ -840,7 +840,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -856,14 +856,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -871,10 +871,10 @@ - An error occurred in a , or object during a streaming operation For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -1113,7 +1113,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -1129,14 +1129,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -1178,7 +1178,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -1194,14 +1194,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -1209,10 +1209,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -1354,7 +1354,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -1370,14 +1370,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -1385,10 +1385,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -1539,7 +1539,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -1553,14 +1553,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -1568,10 +1568,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -1821,7 +1821,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -1837,14 +1837,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -1852,10 +1852,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -1988,7 +1988,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -2004,14 +2004,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -2019,10 +2019,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -2275,7 +2275,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -2291,14 +2291,14 @@ Any error that occurred while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. is set to true and a parameter with direction Output or InputOutput has been added to the collection. @@ -2306,10 +2306,10 @@ - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -2437,7 +2437,7 @@ - For more information, see Configuring parameters. + For more information, see Configuring parameters. @@ -2550,7 +2550,7 @@ SELECT * FROM Customers WHERE CustomerID = @CustomerID - For more information, see Configuring parameters. + For more information, see Configuring parameters. @@ -2912,7 +2912,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -2928,18 +2928,18 @@ An exception occurred while executing the command against a locked row. This exception is not generated when you are using Microsoft .NET Framework version 1.0. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -2954,7 +2954,7 @@ - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. For long-running queries on the server, consider using due to a known issue with canceling queries via a cancellation token. Also, consider canceling execution using the method. @@ -2963,7 +2963,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -2979,7 +2979,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -2989,15 +2989,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3061,7 +3061,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3077,7 +3077,7 @@ An exception occurred while executing the command against a locked row. This exception is not generated when you are using Microsoft .NET Framework version 1.0. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3087,15 +3087,15 @@ The current state of the connection is closed. requires an open . - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3161,7 +3161,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3172,16 +3172,16 @@ - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3193,7 +3193,7 @@ - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. For long-running queries on the server, consider using due to a known issue with canceling queries via a cancellation token. Also, consider canceling execution using the method. @@ -3202,7 +3202,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3221,7 +3221,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3231,15 +3231,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3253,12 +3253,12 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3277,7 +3277,7 @@ Calling more than once for the same instance before task completion. - closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3287,15 +3287,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3309,12 +3309,12 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3333,7 +3333,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3343,15 +3343,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3368,12 +3368,12 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3392,7 +3392,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3402,15 +3402,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3459,7 +3459,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3475,18 +3475,18 @@ An exception occurred while executing the command against a locked row. This exception is not generated when you are using Microsoft .NET Framework version 1.0. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3501,7 +3501,7 @@ - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. For long-running queries on the server, consider using due to a known issue with canceling queries via a cancellation token. Also, consider canceling execution using the method. @@ -3510,7 +3510,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3526,7 +3526,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3536,15 +3536,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3598,7 +3598,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3614,18 +3614,18 @@ An exception occurred while executing the command against a locked row. This exception is not generated when you are using Microsoft .NET Framework version 1.0. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3638,7 +3638,7 @@ - The returned by this method does not support asynchronous operations. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + The returned by this method does not support asynchronous operations. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. For long-running queries on the server, consider using due to a known issue with canceling queries via a cancellation token. Also, consider canceling execution using the method. @@ -3647,7 +3647,7 @@ - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3663,7 +3663,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3673,15 +3673,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3695,12 +3695,12 @@ A task representing the asynchronous operation. - The returned by this method does not support asynchronous operations. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + The returned by this method does not support asynchronous operations. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. - A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. + A other than Binary or VarBinary was used when was set to . For more information about streaming, see SqlClient Streaming Support. A other than Char, NChar, NVarChar, VarChar, or Xml was used when was set to . @@ -3716,7 +3716,7 @@ Calling more than once for the same instance before task completion. - The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The closed or dropped during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3726,15 +3726,15 @@ SQL Server returned an error while executing the command text. - A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + A timeout occurred during a streaming operation. For more information about streaming, see SqlClient Streaming Support. - An error occurred in a , or object during a streaming operation.For more information about streaming, see SqlClient Streaming Support. + An error occurred in a , or object during a streaming operation.For more information about streaming, see SqlClient Streaming Support. - The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. + The , or object was closed during a streaming operation. For more information about streaming, see SqlClient Streaming Support. @@ -3833,7 +3833,7 @@ The command timeout restarts for each execution of a command within the retry logic and after applying the retry time delay. There is no timing overlap between these two actions. - The default retry logic provider is not enabled unless it is configured in an application configuration file. For more information, see Configurable retry logic configuration file. + The default retry logic provider is not enabled unless it is configured in an application configuration file. For more information, see Configurable retry logic configuration file. A command with isn't compatible with the built-in retry logic. The underlying connection is immediately closed after the first execution attempt and is no longer available for subsequent retries. @@ -4143,7 +4143,7 @@ If the parameters in the collection do not match the requirements of the query to be executed, an error may result. - For more information, see Configuring parameters. + For more information, see Configuring parameters. @@ -4322,7 +4322,7 @@ The default value is unless the command is automatically generated (as in the case of the ), in which case the default is . - For more information about using the UpdatedRowSource property, see DataAdapter Parameters. + For more information about using the UpdatedRowSource property, see DataAdapter Parameters. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlCommandBuilder.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlCommandBuilder.xml index 5cf4867488..dbe76c374a 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlCommandBuilder.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlCommandBuilder.xml @@ -165,7 +165,7 @@ You can only use DeriveParameters with stored procedures. You cannot use DeriveParameters with extended stored procedures. You cannot use DeriveParameters to populate the with arbitrary Transact-SQL statements, such as a parameterized SELECT statement. - For more information, see Configuring parameters. + For more information, see Configuring parameters. @@ -201,7 +201,7 @@ After the SQL statement is first generated, the application must explicitly call if it changes the statement in any way. Otherwise, the will still be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either or . - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -240,7 +240,7 @@ - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -262,7 +262,7 @@ After the Transact-SQL statement is first generated, the application must explicitly call if it changes the statement in any way. Otherwise, the will still be using information from the previous statement, which might not be correct. The Transact-SQL statements are first generated when the application calls either or . - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -301,7 +301,7 @@ - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -379,7 +379,7 @@ After the Transact-SQL statement is first generated, the application must explicitly call if it changes the statement in any way. Otherwise, the will still be using information from the previous statement, which might not be correct. The Transact-SQL statements are first generated when the application calls either or . - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -418,7 +418,7 @@ - For more information, see Generating Commands with CommandBuilders. + For more information, see Generating Commands with CommandBuilders. @@ -516,13 +516,13 @@ The unquoted identifier, with embedded quotes properly unescaped. - + Connecting and Retrieving Data in ADO.NET - + Using the .NET Framework Data Provider for SQL Server - + Overview of the SqlClient driver diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlCommandColumnEncryptionSetting.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlCommandColumnEncryptionSetting.xml index ddd254827a..8bf2f14a02 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlCommandColumnEncryptionSetting.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlCommandColumnEncryptionSetting.xml @@ -2,7 +2,7 @@ - Note that these settings cannot be used to bypass encryption and gain access to plaintext data. For details, see Always Encrypted (Database Engine). + Note that these settings cannot be used to bypass encryption and gain access to plaintext data. For details, see Always Encrypted (Database Engine). diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml index c8c5513ea5..b7897f045f 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml @@ -78,13 +78,13 @@ 10929 - Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later. + Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server. Otherwise, please try again later. 10928 - Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. + Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlConnection.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlConnection.xml index f7ca3d1237..b34a61386b 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlConnection.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlConnection.xml @@ -18,7 +18,7 @@ If the goes out of scope, it won't be closed. Therefore, you must explicitly close the connection by calling or . and are functionally equivalent. If the connection pooling value Pooling is set to true or yes, the underlying connection is returned back to the connection pool. On the other hand, if Pooling is set to false or no, the underlying connection to the server is actually closed. - Login and logout events will not be raised on the server when a connection is fetched from or returned to the connection pool, because the connection is not actually closed when it is returned to the connection pool. For more information, see SQL Server Connection Pooling (ADO.NET). + Login and logout events will not be raised on the server when a connection is fetched from or returned to the connection pool, because the connection is not actually closed when it is returned to the connection pool. For more information, see SQL Server Connection Pooling (ADO.NET). To ensure that connections are always closed, open the connection inside of a using block, as shown in the following code fragment. Doing so ensures that the connection is automatically closed when the code exits the block. @@ -37,11 +37,11 @@ } - To deploy high-performance applications, you must use connection pooling. When you use the .NET Framework Data Provider for SQL Server, you do not have to enable connection pooling because the provider manages this automatically, although you can modify some settings. For more information, see SQL Server Connection Pooling (ADO.NET). + To deploy high-performance applications, you must use connection pooling. When you use the .NET Framework Data Provider for SQL Server, you do not have to enable connection pooling because the provider manages this automatically, although you can modify some settings. For more information, see SQL Server Connection Pooling (ADO.NET). - If a is generated by the method executing a , the remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server ordinarily closes the . However, the user can reopen the connection and continue. An application that creates an instance of the object can require all direct and indirect callers to have sufficient permission to the code by setting declarative or imperative security demands. makes security demands using the object. Users can verify that their code has sufficient permissions by using the object. Users and administrators can also use the Caspol.exe (Code Access Security Policy Tool) to modify security policy at the machine, user, and enterprise levels. For more information, see Security in .NET. For an example demonstrating how to use security demands, see Code Access Security and ADO.NET. - For more information about handling warning and informational messages from the server, see Connection Events. For more information about SQL Server engine errors and error messages, see Database Engine Events and Errors. + If a is generated by the method executing a , the remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server ordinarily closes the . However, the user can reopen the connection and continue. An application that creates an instance of the object can require all direct and indirect callers to have sufficient permission to the code by setting declarative or imperative security demands. makes security demands using the object. Users can verify that their code has sufficient permissions by using the object. Users and administrators can also use the Caspol.exe (Code Access Security Policy Tool) to modify security policy at the machine, user, and enterprise levels. For more information, see Security in .NET. For an example demonstrating how to use security demands, see Code Access Security and ADO.NET. + For more information about handling warning and informational messages from the server, see Connection Events. For more information about SQL Server engine errors and error messages, see Database Engine Events and Errors. You can force TCP instead of shared memory. You can do that by prefixing tcp: to the server name in the connection string or you can use localhost. @@ -379,7 +379,7 @@ When your query returns a large amount of data and calls , a is thrown because SQL Server does not allow parallel transactions when using MARS. To avoid this problem, always associate a transaction with the command, the connection, or both before any readers are open. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). @@ -480,10 +480,10 @@ This command maps to the SQL Server implementation of BEGIN TRANSACTION. You must explicitly commit or roll back the transaction using the or method. To make sure that the .NET Framework Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server. - After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see Transaction Isolation Levels. + After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see Transaction Isolation Levels. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). When your query returns a large amount of data and calls , a is thrown because SQL Server does not allow parallel transactions when using MARS. To avoid this problem, always associate a transaction with the command, the connection, or both before any readers are open. @@ -580,7 +580,7 @@ - This command maps to the SQL Server implementation of BEGIN TRANSACTION. The length of the parameter must not exceed 32 characters; otherwise an exception will be thrown. The value in the parameter can be used in later calls to and in the savePoint parameter of the method. You must explicitly commit or roll back the transaction using the or method. To make sure that the .NET Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server. For more information on SQL Server transactions, see Transactions (Transact-SQL). + This command maps to the SQL Server implementation of BEGIN TRANSACTION. The length of the parameter must not exceed 32 characters; otherwise an exception will be thrown. The value in the parameter can be used in later calls to and in the savePoint parameter of the method. You must explicitly commit or roll back the transaction using the or method. To make sure that the .NET Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server. For more information on SQL Server transactions, see Transactions (Transact-SQL). When your query returns a large amount of data and calls , a is thrown because SQL Server does not allow parallel transactions when using MARS. To avoid this problem, always associate a transaction with the command, the connection, or both before any readers are open. @@ -688,10 +688,10 @@ This command maps to the SQL Server implementation of BEGIN TRANSACTION. The value in the parameter can be used in later calls to and in the savePoint parameter of the method. You must explicitly commit or roll back the transaction using the or method. To make sure that the SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server. - After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see Transaction Isolation Levels. + After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see Transaction Isolation Levels. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). When your query returns a large amount of data and calls , a is thrown because SQL Server does not allow parallel transactions when using MARS. To avoid this problem, always associate a transaction with the command, the connection, or both before any readers are open. @@ -1095,7 +1095,7 @@ works regardless of which version of the server you connect to, but extended events logs and entry on connectivity ring buffer errors will not be present in SQL Server 2008 R2 and earlier. - You can locate the connection ID in the extended events log to see if the failure was on the server if the extended event for logging connection ID is enabled. You can also locate the connection ID in the connection ring buffer (Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer) for certain connection errors. If the connection ID is not in the connection ring buffer, you can assume a network error. + You can locate the connection ID in the extended events log to see if the failure was on the server if the extended event for logging connection ID is enabled. You can also locate the connection ID in the connection ring buffer (Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer) for certain connection errors. If the connection ID is not in the connection ring buffer, you can assume a network error. @@ -1114,10 +1114,10 @@ An application can call more than one time. No exception is generated. If the goes out of scope, it won't be closed. Therefore, you must explicitly close the connection by calling Close or Dispose. Close and Dispose are functionally equivalent. If the connection pooling value Pooling is set to true or yes, the underlying connection is returned back to the connection pool. On the other hand, if Pooling is set to false or no, the underlying connection to the server is closed. - Login and logout events will not be raised on the server when a connection is fetched from or returned to the connection pool, because the connection is not actually closed when it is returned to the connection pool. For more information, see SQL Server Connection Pooling (ADO.NET). + Login and logout events will not be raised on the server when a connection is fetched from or returned to the connection pool, because the connection is not actually closed when it is returned to the connection pool. For more information, see SQL Server Connection Pooling (ADO.NET). - Do not call Close or Dispose on a Connection, a DataReader, or any other managed object in the Finalize method of your class. In a finalizer, you should only release unmanaged resources that your class owns directly. If your class does not own any unmanaged resources, do not include a Finalize method in your class definition. For more information, see Garbage Collection. + Do not call Close or Dispose on a Connection, a DataReader, or any other managed object in the Finalize method of your class. In a finalizer, you should only release unmanaged resources that your class owns directly. If your class does not own any unmanaged resources, do not include a Finalize method in your class definition. For more information, see Garbage Collection. @@ -1167,7 +1167,7 @@ - Gets or sets the time-to-live for column encryption key entries in the column encryption key cache for the Always Encrypted feature. The default value is 2 hours. 0 means no caching at all. + Gets or sets the time-to-live for column encryption key entries in the column encryption key cache for the Always Encrypted feature. The default value is 2 hours. 0 means no caching at all. The time interval. @@ -1175,7 +1175,7 @@ - Gets or sets a value that indicates whether query metadata caching is enabled (true) or not (false) for parameterized queries running against Always Encrypted enabled databases. The default value is true. + Gets or sets a value that indicates whether query metadata caching is enabled (true) or not (false) for parameterized queries running against Always Encrypted enabled databases. The default value is true. Returns true if query metadata caching is enabled; otherwise false. true is the default. @@ -1218,7 +1218,7 @@ "Persist Security Info=False;Integrated Security=true;Initial Catalog=Northwind;server=(local)" - Use the new to construct valid connection strings at run time. For more information, see Connection String Builders. The property can be set only when the connection is closed. Many of the connection string values have corresponding read-only properties. When the connection string is set, these properties are updated, except when an error is detected. In this case, none of the properties are updated. properties return only those settings that are contained in the . To connect to a local computer, specify "(local)" for the server. If a server name is not specified, a connection will be attempted to the default instance on the local computer. Resetting the on a closed connection resets all connection string values (and related properties) including the password. For example, if you set a connection string that includes "Database= AdventureWorks", and then reset the connection string to Data Source=myserver;Integrated Security=true, the property is no longer set to "AdventureWorks". The connection string is parsed immediately after being set. If errors in syntax are found when parsing, a runtime exception, such as , is generated. Other errors can be found only when an attempt is made to open the connection. The basic format of a connection string includes a series of keyword/value pairs separated by semicolons. The equal sign (=) connects each keyword and its value. To include values that contain a semicolon, single-quote character, or double-quote character, the value must be enclosed in double quotation marks. If the value contains both a semicolon and a double-quote character, the value can be enclosed in single quotation marks. The single quotation mark is also useful if the value starts with a double-quote character. Conversely, the double quotation mark can be used if the value starts with a single quotation mark. If the value contains both single-quote and double-quote characters, the quotation mark character used to enclose the value must be doubled every time it occurs within the value. To include preceding or trailing spaces in the string value, the value must be enclosed in either single quotation marks or double quotation marks. Any leading or trailing spaces around integer, Boolean, or enumerated values are ignored, even if enclosed in quotation marks. However, spaces within a string literal keyword or value are preserved. Single or double quotation marks may be used within a connection string without using delimiters (for example, Data Source= my'Server or Data Source= my"Server), unless a quotation mark character is the first or last character in the value. Keywords are not case-sensitive. The following table lists the valid names for keyword values within the . + Use the new to construct valid connection strings at run time. For more information, see Connection String Builders. The property can be set only when the connection is closed. Many of the connection string values have corresponding read-only properties. When the connection string is set, these properties are updated, except when an error is detected. In this case, none of the properties are updated. properties return only those settings that are contained in the . To connect to a local computer, specify "(local)" for the server. If a server name is not specified, a connection will be attempted to the default instance on the local computer. Resetting the on a closed connection resets all connection string values (and related properties) including the password. For example, if you set a connection string that includes "Database= AdventureWorks", and then reset the connection string to Data Source=myserver;Integrated Security=true, the property is no longer set to "AdventureWorks". The connection string is parsed immediately after being set. If errors in syntax are found when parsing, a runtime exception, such as , is generated. Other errors can be found only when an attempt is made to open the connection. The basic format of a connection string includes a series of keyword/value pairs separated by semicolons. The equal sign (=) connects each keyword and its value. To include values that contain a semicolon, single-quote character, or double-quote character, the value must be enclosed in double quotation marks. If the value contains both a semicolon and a double-quote character, the value can be enclosed in single quotation marks. The single quotation mark is also useful if the value starts with a double-quote character. Conversely, the double quotation mark can be used if the value starts with a single quotation mark. If the value contains both single-quote and double-quote characters, the quotation mark character used to enclose the value must be doubled every time it occurs within the value. To include preceding or trailing spaces in the string value, the value must be enclosed in either single quotation marks or double quotation marks. Any leading or trailing spaces around integer, Boolean, or enumerated values are ignored, even if enclosed in quotation marks. However, spaces within a string literal keyword or value are preserved. Single or double quotation marks may be used within a connection string without using delimiters (for example, Data Source= my'Server or Data Source= my"Server), unless a quotation mark character is the first or last character in the value. Keywords are not case-sensitive. The following table lists the valid names for keyword values within the . @@ -1251,7 +1251,7 @@ Declares the application workload type when connecting to a server. Possible values are ReadOnly and ReadWrite. For example: ApplicationIntent=ReadOnly - For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. + For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. @@ -1324,7 +1324,7 @@ N/A - The authentication method used for Connecting to SQL Database By Using Azure Active Directory Authentication. + The authentication method used for Connect with Microsoft Entra to Azure SQL resources. Valid values are: @@ -1341,7 +1341,7 @@ Sql Password - For additional information see Using Azure Active Directory authentication with SqlClient. + For additional information see Using Azure Active Directory authentication with SqlClient. @@ -1349,7 +1349,7 @@ Column Encryption Setting disabled - Enables or disables Always Encrypted functionality for the connection. Supported values are: enabled and disabled + Enables or disables Always Encrypted functionality for the connection. Supported values are: enabled and disabled @@ -1442,7 +1442,7 @@ You can also connect to a LocalDB database as follows: server=(localdb)\\myInstance - For more information about LocalDB, see SqlClient Support for LocalDB. + For more information about LocalDB, see SqlClient Support for LocalDB. Data Source must use the TCP format or the Named Pipes format. @@ -1511,7 +1511,7 @@ versions 1 - 4: true / yes and false / no - versions 5+: true / yes / mandatory, false / no / optional and strict. When true, TLS encryption is used for all data sent between the client and server if the server has a certificate installed. When strict, TDS 8.0 TLS encryption is used and the TrustServerCertificate setting is ignored and treated as false. For more information, see Connection String Syntax. + versions 5+: true / yes / mandatory, false / no / optional and strict. When true, TLS encryption is used for all data sent between the client and server if the server has a certificate installed. When strict, TDS 8.0 TLS encryption is used and the TrustServerCertificate setting is ignored and treated as false. For more information, see Connection String Syntax. @@ -1678,7 +1678,7 @@ Recognized values are true and false. - For more information, see Multiple Active Result Sets (MARS). + For more information, see Multiple Active Result Sets (MARS). @@ -1695,7 +1695,7 @@ MultiSubnetFailover=True - The default is False. For more information about SqlClient's support for Always On AGs, see SqlClient Support for High Availability, Disaster Recovery. + The default is False. For more information about SqlClient's support for Always On AGs, see SqlClient Support for High Availability, Disaster Recovery. @@ -1887,7 +1887,7 @@ false - When set to true, TLS is used to encrypt the channel when bypassing walking the certificate chain to validate trust. If TrustServerCertificate is set to true and Encrypt is set to false, the channel is not encrypted. Recognized values are true, false, yes, and no. For more information, see Connection String Syntax. + When set to true, TLS is used to encrypt the channel when bypassing walking the certificate chain to validate trust. If TrustServerCertificate is set to true and Encrypt is set to false, the channel is not encrypted. Recognized values are true, false, yes, and no. For more information, see Connection String Syntax. @@ -1895,7 +1895,7 @@ N/A - A string value that indicates the type system the application expects. The functionality available to a client application is dependent on the version of SQL Server and the compatibility level of the database. Explicitly setting the type system version that the client application was written for avoids potential problems that could cause an application to break if a different version of SQL Server is used. Note: The type system version cannot be set for common language runtime (CLR) code executing in-process in SQL Server. For more information, see SQL Server Common Language Runtime Integration. + A string value that indicates the type system the application expects. The functionality available to a client application is dependent on the version of SQL Server and the compatibility level of the database. Explicitly setting the type system version that the client application was written for avoids potential problems that could cause an application to break if a different version of SQL Server is used. Note: The type system version cannot be set for common language runtime (CLR) code executing in-process in SQL Server. For more information, see SQL Server Common Language Runtime Integration. Possible values are: @@ -1947,7 +1947,7 @@ - The following list contains the valid names for connection pooling values within the . For more information, see SQL Server Connection Pooling (ADO.NET). + The following list contains the valid names for connection pooling values within the . For more information, see SQL Server Connection Pooling (ADO.NET). Connection Lifetime (or Load Balance Timeout) @@ -1966,7 +1966,7 @@ Universal data link (UDL) files are not supported for the .NET Framework Data Provider for SQL Server. - In this release, the application should use caution when constructing a connection string based on user input (for example when retrieving user ID and password information from a dialog box, and appending it to the connection string). The application should make sure that a user cannot embed additional connection string parameters in these values (for example, entering a password as "validpassword;database=somedb" in an attempt to attach to a different database). If you need to construct connection strings based on user input, use the new , which validates the connection string and helps to eliminate this problem. See Connection String Builders for more information. + In this release, the application should use caution when constructing a connection string based on user input (for example when retrieving user ID and password information from a dialog box, and appending it to the connection string). The application should make sure that a user cannot embed additional connection string parameters in these values (for example, entering a password as "validpassword;database=somedb" in an attempt to attach to a different database). If you need to construct connection strings based on user input, use the new , which validates the connection string and helps to eliminate this problem. See Connection String Builders for more information. @@ -2287,7 +2287,7 @@ - You can use the method to enlist in a distributed transaction. Because it enlists a connection in a instance, takes advantage of functionality available in the namespace for managing distributed transactions, making it preferable to for this purpose. For more information, see Distributed Transactions. + You can use the method to enlist in a distributed transaction. Because it enlists a connection in a instance, takes advantage of functionality available in the namespace for managing distributed transactions, making it preferable to for this purpose. For more information, see Distributed Transactions. You can continue to enlist in an existing distributed transaction using the EnlistDistributedTransaction method if auto-enlistment is disabled. Enlisting in an existing distributed transaction makes sure that, if the transaction is committed or rolled back, modifications made by the code at the data source are also committed or rolled back. EnlistDistributedTransaction returns an exception if the has already started a transaction using . However, if the transaction is a local transaction started at the data source (for example, by explicitly executing the BEGIN TRANSACTION statement using an object), EnlistDistributedTransaction rolls back the local transaction and enlists in the existing distributed transaction as requested. You do not receive notice that the local transaction was rolled back, and are responsible for managing any local transactions not started using . @@ -2302,7 +2302,7 @@ Enlists in the specified transaction as a distributed transaction. - You can use the method to enlist in a distributed transaction. Because it enlists a connection in a instance, takes advantage of functionality available in the namespace for managing distributed transactions, making it preferable to , which uses a object (from namespace). It also has slightly different semantics: once a connection is explicitly enlisted on a transaction, it cannot be unenlisted or enlisted in another transaction until the first transaction finishes. For more information about distributed transactions, see Distributed Transactions. + You can use the method to enlist in a distributed transaction. Because it enlists a connection in a instance, takes advantage of functionality available in the namespace for managing distributed transactions, making it preferable to , which uses a object (from namespace). It also has slightly different semantics: once a connection is explicitly enlisted on a transaction, it cannot be unenlisted or enlisted in another transaction until the first transaction finishes. For more information about distributed transactions, see Distributed Transactions. @@ -2320,13 +2320,13 @@ An error with a severity level of 17 or above that causes the server to stop processing the command needs to be handled as an exception. In this case, an exception is thrown regardless of how the error is handled in the event. - For more information on working with events, see Connection Events. For more information on errors generated by the SQL Server engine, see Database Engine Errors. + For more information on working with events, see Connection Events. For more information on errors generated by the SQL Server engine, see Database Engine Errors. - Returns schema information for the data source of this . For more information about scheme, see SQL Server Schema Collections. + Returns schema information for the data source of this . For more information about scheme, see SQL Server Schema Collections. A that contains schema information. @@ -2431,7 +2431,7 @@ GO - How to Get Schema Information from Database has C# and Visual Basic versions of this code sample in a Visual Studio project. + How to Get Schema Information from Database has C# and Visual Basic versions of this code sample in a Visual Studio project. @@ -2655,8 +2655,8 @@ Clients that want to process warnings or informational messages sent by the server should create an delegate to listen to this event. - The event occurs when a message with a severity of 10 or less is returned by SQL Server. Messages that have a severity between 11 and 20 raise an error and messages that have a severity over 20 causes the connection to close. For more information on SQL Server error levels, see Database Engine Error Severities. - For more information and an example, see Connection Events. + The event occurs when a message with a severity of 10 or less is returned by SQL Server. Messages that have a severity between 11 and 20 raise an error and messages that have a severity over 20 causes the connection to close. For more information on SQL Server error levels, see Database Engine Error Severities. + For more information and an example, see Connection Events. @@ -2838,7 +2838,7 @@ After calling , must return until the returned is completed. Then, if the connection was successful, must return . If the connection fails, must return . - A call to will attempt to cancel or close the corresponding call. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + A call to will attempt to cancel or close the corresponding call. For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. @@ -2865,7 +2865,7 @@ If an application performs bulk copy operations, or sends or receives lots of text or image data, a packet size larger than the default may improve efficiency because it causes fewer network read and write operations. If an application sends and receives small amounts of information, you can set the packet size to 512 bytes (using the Packet Size value in the ), which is sufficient for most data transfer operations. For most applications, the default packet size is best. may be a value in the range of 512 and 32767 bytes. An exception is generated if the value is outside this range. - Setting the default value to a number greater than 8000 will cause the packets to use the MultiPage allocator on the instance of SQL Server instead of the much more efficient SinglePage allocator, reducing the overall scalability of the SQL Server. For more information on how SQL Server uses memory, see Memory Management Architecture Guide. + Setting the default value to a number greater than 8000 will cause the packets to use the MultiPage allocator on the instance of SQL Server instead of the much more efficient SinglePage allocator, reducing the overall scalability of the SQL Server. For more information on how SQL Server uses memory, see Memory Management Architecture Guide. @@ -3024,7 +3024,7 @@ The connection timeout restarts for each execution of a connection open. There is no timing overlap between these two actions. - The default retry logic provider is not enabled unless it is configured in an application configuration file. For more information, see Configurable retry logic and configuration file. + The default retry logic provider is not enabled unless it is configured in an application configuration file. For more information, see Configurable retry logic and configuration file. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionColumnEncryptionSetting.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionColumnEncryptionSetting.xml index 68dc82a65a..20983af932 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionColumnEncryptionSetting.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionColumnEncryptionSetting.xml @@ -2,7 +2,7 @@ - Note that these settings cannot be used to bypass encryption and gain access to plaintext data. For details, see Always Encrypted (Database Engine). + Note that these settings cannot be used to bypass encryption and gain access to plaintext data. For details, see Always Encrypted (Database Engine). diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionStringBuilder.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionStringBuilder.xml index 7f4d9a11a4..299c42226c 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionStringBuilder.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlConnectionStringBuilder.xml @@ -174,7 +174,7 @@ - Declares the application workload type when connecting to a database in an SQL Server Availability Group. You can set the value of this property with . For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. + Declares the application workload type when connecting to a database in an SQL Server Availability Group. You can set the value of this property with . For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. Returns the current value of the property. @@ -187,7 +187,7 @@ The default value is ApplicationIntent.ReadWrite . - + Overview of the SqlClient driver @@ -321,10 +321,10 @@ To set the value to null, use . - + Working with Connection Strings - + Overview of the SqlClient driver @@ -341,13 +341,13 @@ - Gets or sets the authentication method used for Connecting to SQL Database By Using Azure Active Directory Authentication. + Gets or sets the authentication method used for Connect with Microsoft Entra to Azure SQL resources. The authentication method of the connection string. - For more information, see Using Azure Active Directory authentication with SqlClient. + For more information, see Connect to Azure SQL with Microsoft Entra authentication and SqlClient. @@ -394,7 +394,7 @@ Gets or sets the column encryption settings for the connection string builder. - The column encryption settings for the connection string builder.This property enables or disables Always Encrypted functionality for the connection. + The column encryption settings for the connection string builder.This property enables or disables Always Encrypted functionality for the connection. @@ -637,7 +637,7 @@ When specifying a local instance, always use (local). To force a protocol, add one of the following prefixes: np:(local), tcp:(local), lpc:(local) . - You can also connect to a LocalDB database as follows: server=(localdb)\\myInstance . For more information about LocalDB, see SqlClient Support for LocalDB . Data Source must use the TCP format or the Named Pipes format. TCP format is as follows: + You can also connect to a LocalDB database as follows: server=(localdb)\\myInstance . For more information about LocalDB, see SqlClient Support for LocalDB . Data Source must use the TCP format or the Named Pipes format. TCP format is as follows: tcp:\<host name>\\<instance name> @@ -737,7 +737,7 @@ This property corresponds to the "Encrypt" key within the connection string. - When is and Encrypt is , or , the server name (or IP address) in a server's TLS certificate must exactly match the server name (or IP address) specified in the connection string. Otherwise, the connection attempt will fail. For information about support for certificates whose subject starts with a wildcard character (*), see Enable encrypted connections to the Database Engine . + When is and Encrypt is , or , the server name (or IP address) in a server's TLS certificate must exactly match the server name (or IP address) specified in the connection string. Otherwise, the connection attempt will fail. For information about support for certificates whose subject starts with a wildcard character (*), see Enable encrypted connections to the Database Engine . Starting from version 4.0, the default value of the property Encrypt is set to while it is for earlier versions. @@ -746,10 +746,10 @@ Starting from version 5.0, the data type is updated to , and the default value of the Encrypt property is set to . - + Working with Connection Strings - + Overview of the SqlClient driver @@ -983,10 +983,10 @@ in every case, because the supplies a fixed-size collection of key/value pairs. - + Working with Connection Strings - + Overview of the SqlClient driver @@ -1132,7 +1132,7 @@ - When true, an application can maintain multiple active result sets (MARS). When false, an application must process or cancel all result sets from one batch before it can execute any other batch on that connection. For more information, see Multiple Active Result Sets (MARS). + When true, an application can maintain multiple active result sets (MARS). When false, an application must process or cancel all result sets from one batch before it can execute any other batch on that connection. For more information, see Multiple Active Result Sets (MARS). The value of the property, or if none has been supplied. @@ -1178,7 +1178,7 @@ - If your application is connecting to an AlwaysOn availability group (AG) on different subnets, setting MultiSubnetFailover=true provides faster detection of and connection to the (currently) active server. For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. + If your application is connecting to an AlwaysOn availability group (AG) on different subnets, setting MultiSubnetFailover=true provides faster detection of and connection to the (currently) active server. For more information about SqlClient support for Always On Availability Groups, see SqlClient Support for High Availability, Disaster Recovery. Returns indicating the current value of the property. @@ -1678,7 +1678,7 @@ When Trust Server Certificate is set to , the transport layer will use TLS to encrypt the channel and bypass walking the certificate chain to validate trust. If Trust Server Certificate is set to and encryption is enforced by target server, the encryption level specified on the server will be used even if Encrypt is set to . The connection will fail otherwise. - For more information, see Encryption Hierarchy and Using Encryption Without Validation. + For more information, see Encryption Hierarchy and Using Encryption Without Validation. @@ -1843,7 +1843,7 @@ This property corresponds to the "User Instance" key within the connection string. - This feature is available only with the SQL Server Express Edition. For more information on user instances, see SQL Server Express User Instances. + This feature is available only with the SQL Server Express Edition. For more information on user instances, see SQL Server Express User Instances. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlCredential.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlCredential.xml index c7a630eb1f..d8005456b6 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlCredential.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlCredential.xml @@ -6,7 +6,7 @@ - Use to get or set a connection's object. Use to change the password for a object. For information on how a object affects connection pool behavior, see SQL Server Connection Pooling (ADO.NET). + Use to get or set a connection's object. Use to change the password for a object. For information on how a object affects connection pool behavior, see SQL Server Connection Pooling (ADO.NET). An exception will be raised if a non-null object is used in a connection with any of the following connection string keywords: @@ -62,7 +62,7 @@ The constructor does not accept null parameters. An string.Empty value is allowed. An attempt to pass a null parameter in the constructor will raise an exception. - + Overview of the SqlClient driver @@ -73,7 +73,7 @@ The password component of the object. - + Overview of the SqlClient driver @@ -84,7 +84,7 @@ The user ID component of the object. - + Overview of the SqlClient driver diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlDataAdapter.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlDataAdapter.xml index 6921841825..8013767227 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlDataAdapter.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlDataAdapter.xml @@ -6,7 +6,7 @@ - The , serves as a bridge between a and SQL Server for retrieving and saving data. The provides this bridge by mapping , which changes the data in the to match the data in the data source, and , which changes the data in the data source to match the data in the , using the appropriate Transact-SQL statements against the data source. The update is performed on a by-row basis. For every inserted, modified, and deleted row, the method determines the type of change that has been performed on it (Insert, Update, or Delete). Depending on the type of change, the Insert, Update, or Delete command template executes to propagate the modified row to the data source. When the fills a , it creates the necessary tables and columns for the returned data if they do not already exist. However, primary key information is not included in the implicitly created schema unless the property is set to . You may also have the create the schema of the , including primary key information, before filling it with data using FillSchema. For more information, see Adding Existing Constraints to a DataSet. is used in conjunction with and to increase performance when connecting to a SQL Server database. + The , serves as a bridge between a and SQL Server for retrieving and saving data. The provides this bridge by mapping , which changes the data in the to match the data in the data source, and , which changes the data in the data source to match the data in the , using the appropriate Transact-SQL statements against the data source. The update is performed on a by-row basis. For every inserted, modified, and deleted row, the method determines the type of change that has been performed on it (Insert, Update, or Delete). Depending on the type of change, the Insert, Update, or Delete command template executes to propagate the modified row to the data source. When the fills a , it creates the necessary tables and columns for the returned data if they do not already exist. However, primary key information is not included in the implicitly created schema unless the property is set to . You may also have the create the schema of the , including primary key information, before filling it with data using FillSchema. For more information, see Adding Existing Constraints to a DataSet. is used in conjunction with and to increase performance when connecting to a SQL Server database. If you are using SQL Server stored procedures to edit or delete data using a DataAdapter, make sure that you do not use SET NOCOUNT ON in the stored procedure definition. This causes the rows affected count returned to be zero, which the DataAdapter interprets as a concurrency conflict. In this event, a will be thrown. @@ -24,7 +24,7 @@ For every column that you propagate to the data source on , a parameter should be added to the InsertCommand, UpdateCommand, or DeleteCommand. The property of the object should be set to the name of the column. This setting indicates that the value of the parameter is not set manually, but is taken from the particular column in the currently processed row. - An will occur if the method is called and the table contains a user-defined type that is not available on the client computer. For more information, see CLR User-Defined Types. + An will occur if the method is called and the table contains a user-defined type that is not available on the client computer. For more information, see CLR User-Defined Types. @@ -599,7 +599,7 @@ - During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. + During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. When is assigned to a previously created , the is not cloned. The maintains a reference to the previously created object. @@ -745,7 +745,7 @@ - During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. + During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. When is assigned to a previously created , the is not cloned. The maintains a reference to the previously created object. @@ -1283,7 +1283,7 @@ - During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. + During , if this property is not set and primary key information is present in the , the can be generated automatically if you set the property and use the . Then, any additional commands that you do not set are generated by the . This generation logic requires key column information to be present in the . For more information, see Generating Commands with CommandBuilders. When is assigned to a previously created , the is not cloned. The maintains a reference to the previously created object. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlDataReader.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlDataReader.xml index 7e64c9180c..ad997ad909 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlDataReader.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlDataReader.xml @@ -78,7 +78,7 @@ - You must ensure the method is called when you are through using the before using the associated for any other purpose. The Close method may either be called directly or through the method, disposing directly or in the context of + You must ensure the method is called when you are through using the before using the associated for any other purpose. The Close method may either be called directly or through the method, disposing directly or in the context of the using statement block. @@ -86,7 +86,7 @@ The Close method populates the values for output parameters, return values and on the by consuming any pending results. This may be a long operation depending on the amount of data to be consumed. If output values, return values, and are not important to your application, the time to close may be shortened by calling the method of the associated object before the Close method is called. - Do not call Close or on a Connection, a DataReader, or any other managed object in the finalizer method of your class. In a finalizer, you should only release unmanaged resources that your class owns directly. If your class does not own any unmanaged resources, do not include a finalizer method in your class definition. For more information, see Garbage Collection. + Do not call Close or on a Connection, a DataReader, or any other managed object in the finalizer method of your class. In a finalizer, you should only release unmanaged resources that your class owns directly. If your class does not own any unmanaged resources, do not include a finalizer method in your class definition. For more information, see Garbage Collection. @@ -509,7 +509,7 @@ UDT, which can be any CLR type marked with . - For more information, see SqlClient Streaming Support. + For more information, see SqlClient Streaming Support. @@ -583,7 +583,7 @@ UDT, which can be any CLR type marked with . - For more information, see SqlClient Streaming Support. + For more information, see SqlClient Streaming Support. @@ -895,7 +895,7 @@ The maximum possible length of a value in the column. For columns that use a fixed-length data type, this is the size of the data type. For nvarchar(MAX), varchar(MAX), and varbinary(MAX) columns stored in a SQL Server database, the maximum size is 2GB. If these columns are stored and accessed as files, the limit on maximum size is imposed by the file system. This value changes when using the Type System Version keyword in the connection string. - For new types they are represented as downlevel types. The MAX data types return the normal 4k for nvarchar and 8000 for varchar. For more information, see the Transact-SQL reference. + For new types they are represented as downlevel types. The MAX data types return the normal 4k for nvarchar and 8000 for varchar. For more information, see the Transact-SQL reference. @@ -1377,7 +1377,7 @@ WriteTimeout - For more information, see SqlClient Streaming Support + For more information, see SqlClient Streaming Support @@ -1444,7 +1444,7 @@ Null values will be returned as an empty (zero bytes) . will raise an exception when used on an object returned by when is in effect. - For more information, see SqlClient Streaming Support. + For more information, see SqlClient Streaming Support. @@ -1585,7 +1585,7 @@ The object returned by does not support asynchronous operations. If you require asynchronous operations on an , cast the XML column to an NVARCHAR(MAX) on the server and use with . exceptions raised from are thrown as exceptions; check the inner exception for the . will raise an exception when used on an object returned by when is in effect. - For more information, see SqlClient Streaming Support. + For more information, see SqlClient Streaming Support. @@ -1700,7 +1700,7 @@ if the specified column value is equivalent to otherwise . - For more information, see SqlClient Streaming Support. + For more information, see SqlClient Streaming Support. @@ -1781,7 +1781,7 @@ A task representing the asynchronous operation. - For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. Calling more than once for the same instance before task completion. @@ -1875,7 +1875,7 @@ If the behavior parameter of is set to Default, ReadAsync reads the entire row before returning the Task. - For more information, including code samples, about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. + For more information, including code samples, about asynchronous programming in the .NET Framework Data Provider for SQL Server, see Asynchronous Programming. When reading large data (binary/text), it is recommended to use for optimal performance. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlDependency.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlDependency.xml index 09e44bb0e8..b4450f5196 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlDependency.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlDependency.xml @@ -9,13 +9,13 @@ is ideal for caching scenarios, where your ASP.NET application or middle-tier service needs to keep certain information cached in memory. allows you to receive notifications when the original data in the database changes so that the cache can be refreshed. - To set up a dependency, you need to associate a object to one or more objects. To receive notifications, you need to subscribe to the event. For more information about the requirements for creating queries for notifications, see Working with Query Notifications. + To set up a dependency, you need to associate a object to one or more objects. To receive notifications, you need to subscribe to the event. For more information about the requirements for creating queries for notifications, see Working with Query Notifications. - was designed to be used in ASP.NET or middle-tier services where there is a relatively small number of servers having dependencies active against the database. It was not designed for use in client applications, where hundreds or thousands of client computers would have objects set up for a single database server. If you are developing an application where you need reliable sub-second notifications when data changes, review the sections Planning an Effective Query Notifications Strategy and Alternatives to Query Notifications in the article + was designed to be used in ASP.NET or middle-tier services where there is a relatively small number of servers having dependencies active against the database. It was not designed for use in client applications, where hundreds or thousands of client computers would have objects set up for a single database server. If you are developing an application where you need reliable sub-second notifications when data changes, review the sections Planning an Effective Query Notifications Strategy and Alternatives to Query Notifications in the article - For more information, see Query Notifications in SQL Server and Building Notification Solutions. + For more information, see Query Notifications in SQL Server and Building Notification Solutions. The event may be generated on a different thread from the thread that initiated command execution. @@ -34,7 +34,7 @@ The constructor initializes the object using the default Service Broker service name and time-out. At some point after construction, you must use the method to associate one or more commands to this object. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. @@ -50,7 +50,7 @@ Internally, this constructor creates an instance of the class, and binds it to a object. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. @@ -74,7 +74,7 @@ Creates a new instance of the class, associates it with the parameter, and specifies notification options and a time-out value. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. The parameter is NULL. @@ -101,7 +101,7 @@ Associates a object with this instance. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. The parameter is null. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlError.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlError.xml index 2ebeb40480..5280e51ffb 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlError.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlError.xml @@ -15,7 +15,7 @@ The remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server usually closes the . However, the user can reopen the connection and continue. In both cases, a is generated by the method executing the command. - For more information on errors generated by SQL Server, see Cause and Resolution of Database Engine Errors. For more information about severity levels, see Database Engine Error Severities. + For more information on errors generated by SQL Server, see Database Engine events and errors. For more information about severity levels, see Database Engine Error Severities. @@ -98,7 +98,7 @@ The remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server usually closes the . However, the user can reopen the connection and continue. In both cases, a is generated by the method executing the command. - For more information on errors generated by SQL Server, see Database Engine Events and Errors. + For more information on errors generated by SQL Server, see Database Engine Events and Errors. @@ -154,7 +154,7 @@ Line numbering starts at 1. If the value is 0, the line number is not applicable. - For more information on errors generated by SQL Server, see Database Engine Events and Errors. + For more information on errors generated by SQL Server, see Database Engine Events and Errors. @@ -203,7 +203,7 @@ Gets the text describing the error. - The text describing the error. For more information on errors generated by SQL Server, see + The text describing the error. For more information on errors generated by SQL Server, see Database Engine Events and Errors . @@ -335,7 +335,7 @@ - For more information on errors generated by SQL Server, see Database Engine Events and Errors. + For more information on errors generated by SQL Server, see Database Engine Events and Errors. @@ -384,7 +384,7 @@ Gets the name of the stored procedure or remote procedure call (RPC) that generated the error. - The name of the stored procedure or RPC. For more information on errors generated by SQL Server, see Database Engine Events and Errors. + The name of the stored procedure or RPC. For more information on errors generated by SQL Server, see Database Engine Events and Errors. @@ -535,7 +535,7 @@ State is only set for errors that are received from the server. - For more information on errors generated by SQL Server, see Understanding Database Engine Errors. + For more information on errors generated by SQL Server, see Understanding Database Engine Errors. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlException.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlException.xml index 7fe2e2e6b9..780fbd95f8 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlException.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlException.xml @@ -15,7 +15,7 @@ The remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server ordinarily closes the . However, the user can reopen the connection and continue. In both cases, a is generated by the method executing the command. - For information about the warning and informational messages sent by SQL Server, see Database Engine Events and Errors. The class maps to SQL Server severity. + For information about the warning and informational messages sent by SQL Server, see Database Engine Events and Errors. The class maps to SQL Server severity. The following is general information on handling exceptions. Your code should catch exceptions to prevent the application from crashing and to allow displaying a relevant error message to the user. You can use database transactions to ensure that the data is consistent regardless of what happens in the client application (including a crash). Features like or the ensure consistent data regardless of exceptions raised by a provider. Transactions can fail, so catch failures and retry the transaction. @@ -150,7 +150,7 @@ This is a wrapper for the property of the first in the property. - If is , the default value for byte is returned. + If is , the default value for byte is returned. @@ -221,7 +221,7 @@ - Represents the client connection ID. For more information, see Data Tracing in ADO.NET. + Represents the client connection ID. For more information, see Data Tracing in ADO.NET. The client connection ID. @@ -242,7 +242,7 @@ The class always contains at least one instance of the class. - This is a wrapper for . For more information on SQL Server engine errors, see Database Engine Events and Errors. + This is a wrapper for . For more information on SQL Server engine errors, see Database Engine Events and Errors. @@ -325,7 +325,7 @@ This is a wrapper for the property of the first in the property. - If is , the default value for int is returned. + If is , the default value for int is returned. @@ -414,10 +414,10 @@ This is a wrapper for the property of the first in the property. - If is , the default value for int is returned. + If is , the default value for int is returned. - For more information on SQL Server engine errors, see Database Engine Events and Errors. + For more information on SQL Server engine errors, see Database Engine Events and Errors. @@ -498,7 +498,7 @@ This is a wrapper for the property of the first in the property. - If is , the default value for string is returned. + If is , the default value for string is returned. @@ -579,7 +579,7 @@ This is a wrapper for the property of the first in the property. - If is , the default value for string is returned. + If is , the default value for string is returned. @@ -751,7 +751,7 @@ - Gets a numeric error code from SQL Server that represents an error, warning or "no data found" message. For more information about how to decode these values, see Database Engine Events and Errors. + Gets a numeric error code from SQL Server that represents an error, warning or "no data found" message. For more information about how to decode these values, see Database Engine Events and Errors. The number representing the error code. @@ -761,7 +761,7 @@ This is a wrapper for the property of the first in the property. - If is , the default value for byte is returned. + If is , the default value for byte is returned. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlInfoMessageEventHandler.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlInfoMessageEventHandler.xml index 80bcd95be0..9938c168b0 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlInfoMessageEventHandler.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlInfoMessageEventHandler.xml @@ -11,7 +11,7 @@ Represents the method that will handle the event of a . - When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. + When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlNotificationSource.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlNotificationSource.xml index ec5c5ef6ff..df56f6b11e 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlNotificationSource.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlNotificationSource.xml @@ -10,7 +10,7 @@ The SqlNotificationSource enumeration is referenced by an instance of the class. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see SQL Server Service Broker and Working with Query Notifications. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlParameter.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlParameter.xml index c439910d87..22a1d92603 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlParameter.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlParameter.xml @@ -2,7 +2,7 @@ - Represents a parameter to a and optionally its mapping to columns. This class cannot be inherited. For more information on parameters, see Configuring parameters + Represents a parameter to a and optionally its mapping to columns. This class cannot be inherited. For more information on parameters, see Configuring parameters @@ -12,7 +12,7 @@ Nameless, also called ordinal, parameters are not supported by the .NET Framework Data Provider for SQL Server. - For more information, along with additional sample code demonstrating how to use parameters, see Commands and Parameters. + For more information, along with additional sample code demonstrating how to use parameters, see Commands and Parameters. @@ -20,7 +20,7 @@ The following example creates multiple instances of through the collection within the . These parameters are used to select data from the data source and put the data in the . - This example assumes that a and a have already been created by using the appropriate schema, commands, and connection. For more information and additional examples on using parameters, see Retrieving and Modifying Data in ADO.NET and Configuring parameters. + This example assumes that a and a have already been created by using the appropriate schema, commands, and connection. For more information and additional examples on using parameters, see Retrieving and Modifying Data in ADO.NET and Configuring parameters. @@ -427,7 +427,7 @@ The and are linked. Therefore, setting the changes the to a supporting . - For a list of the supported data types, see the appropriate member. For more information, see DataAdapter Parameters. + For a list of the supported data types, see the appropriate member. For more information, see DataAdapter Parameters. @@ -483,9 +483,9 @@ The following example creates a and sets some of its properties. - Commands and Parameters - DataAdapter Parameters - SQL Server and ADO.NET + Commands and Parameters + DataAdapter Parameters + SQL Server and ADO.NET @@ -494,7 +494,7 @@ - Enforces encryption of a parameter when using Always Encrypted. If SQL Server informs the driver that the parameter does not need to be encrypted, the query using the parameter will fail. This property provides additional protection against security attacks that involve a compromised SQL Server providing incorrect encryption metadata to the client, which may lead to data disclosure. + Enforces encryption of a parameter when using Always Encrypted. If SQL Server informs the driver that the parameter does not need to be encrypted, the query using the parameter will fail. This property provides additional protection against security attacks that involve a compromised SQL Server providing incorrect encryption metadata to the client, which may lead to data disclosure. if the parameter has a force column encryption; otherwise, . @@ -742,7 +742,7 @@ For fixed length data types, the value of Size is ignored. It can be retrieved for informational purposes, and returns the maximum amount of bytes the provider uses when transmitting the value of the parameter to the server. - For information about streaming, see SqlClient Streaming Support. + For information about streaming, see SqlClient Streaming Support. @@ -774,7 +774,7 @@ When SourceColumn is set to anything other than an empty string, the value of the parameter is retrieved from the column with the SourceColumn name. If is set to , the value is taken from the . If is set to , the value is taken from the data source. A of is a combination of both. - For more information about how to use the SourceColumn property, see DataAdapter Parameters and Updating Data Sources with DataAdapters. + For more information about how to use the SourceColumn property, see DataAdapter Parameters and Updating Data Sources with DataAdapters. @@ -853,10 +853,10 @@ The SqlDbType and are linked. Therefore, setting the changes the SqlDbType to a supporting . - For a list of the supported data types, see the appropriate member. For more information, see DataAdapter Parameters. + For a list of the supported data types, see the appropriate member. For more information, see DataAdapter Parameters. - For information about streaming, see SqlClient Streaming Support. + For information about streaming, see SqlClient Streaming Support. @@ -887,7 +887,7 @@ Use the property to return parameter values as common language runtime (CLR) types. - For information about streaming, see SqlClient Streaming Support. + For information about streaming, see SqlClient Streaming Support. @@ -926,7 +926,7 @@ A that represents the fully qualified name of a user-defined type in the database. - For a sample demonstrating UdtTypeName, see Retrieving UDT Data. + For a sample demonstrating UdtTypeName, see Retrieving UDT Data. @@ -956,7 +956,7 @@ The Value property is overwritten by . - For information about streaming, see SqlClient Streaming Support. + For information about streaming, see SqlClient Streaming Support. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlParameterCollection.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlParameterCollection.xml index 59853057da..e38f8d02c0 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlParameterCollection.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlParameterCollection.xml @@ -9,7 +9,7 @@ If the command contains an ad hoc SQL statement, as opposed to a stored-procedure name, the number of the parameters in the collection must be equal to the number of parameter placeholders within the command text, or SQL Server raises an error. With a stored procedure, all the parameters declared in the stored procedure without a default value must be provided. Parameters declared with a default value are optional. This lets you specify a value other than the default. - For more information with additional sample code demonstrating how to use parameters, see Commands and Parameters. + For more information with additional sample code demonstrating how to use parameters, see Commands and Parameters. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatedEventHandler.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatedEventHandler.xml index ac66308043..f45bae93d6 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatedEventHandler.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatedEventHandler.xml @@ -15,7 +15,7 @@ The handler is not required to perform any action, and your code should avoid generating exceptions or allowing exceptions to propagate to the calling method. Any exceptions that do reach the caller are ignored. - When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. + When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatingEventHandler.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatingEventHandler.xml index e861f4c855..7258f30944 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatingEventHandler.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlRowUpdatingEventHandler.xml @@ -18,7 +18,7 @@ The handler may use the to influence the processing of the updates. For example, the handler may opt to skip the update of the current row or skip the update of all remaining rows. Note that the rows are updated in the order that they were received from the data source. - When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. + When you create a delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event handler delegates, see Handling and Raising Events. diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlTransaction.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlTransaction.xml index 2a7aae8798..9329b62e68 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlTransaction.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlTransaction.xml @@ -12,7 +12,7 @@ Try / Catch exception handling should always be used when committing or rolling back a . Both and generate an if the connection is terminated or if the transaction has already been rolled back on the server. - For more information on SQL Server transactions, see Explicit Transactions and Coding Efficient Transactions + For more information on SQL Server transactions, see Explicit Transactions @@ -99,13 +99,13 @@ - The method is equivalent to the Transact-SQL COMMIT TRANSACTION statement. You cannot roll back a transaction once it has been committed, because all modifications have become a permanent part of the database. For more information, see COMMIT TRANSACTION (Transact-SQL). + The method is equivalent to the Transact-SQL COMMIT TRANSACTION statement. You cannot roll back a transaction once it has been committed, because all modifications have become a permanent part of the database. For more information, see COMMIT TRANSACTION (Transact-SQL). Try / Catch exception handling should always be used when committing or rolling back a . Both Commit and generates an if the connection is terminated or if the transaction has already been rolled back on the server. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). @@ -245,7 +245,7 @@ Parallel transactions are not supported. Therefore, the applies to the whole transaction. - For more information on SQL Server isolation levels, see Transaction Isolation Levels. + For more information on SQL Server isolation levels, see Transaction Isolation Levels. @@ -260,7 +260,7 @@ - The Rollback method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see ROLLBACK TRANSACTION (Transact-SQL). + The Rollback method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see ROLLBACK TRANSACTION (Transact-SQL). The transaction can only be rolled back from a pending state (after has been called, but before is called). The transaction is rolled back in the event it is disposed before or Rollback is called. @@ -269,7 +269,7 @@ Try / Catch exception handling should always be used when rolling back a transaction. A Rollback generates an if the connection is terminated or if the transaction has already been rolled back on the server. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). @@ -368,7 +368,7 @@ - The method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see Transactions (Transact-SQL). + The method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see Transactions (Transact-SQL). The transaction can only be rolled back from a pending state (after has been called, but before is called). The transaction is rolled back if it is disposed before or Rollback is called. @@ -377,7 +377,7 @@ Try / Catch exception handling should always be used when rolling back a transaction. A Rollback generates an if the connection is terminated or if the transaction has already been rolled back on the server. - For more information on SQL Server transactions, see Transactions (Transact-SQL). + For more information on SQL Server transactions, see Transactions (Transact-SQL). diff --git a/doc/snippets/Microsoft.Data.SqlTypes/SqlFileStream.xml b/doc/snippets/Microsoft.Data.SqlTypes/SqlFileStream.xml index 1abd1847df..4687ea7c1d 100644 --- a/doc/snippets/Microsoft.Data.SqlTypes/SqlFileStream.xml +++ b/doc/snippets/Microsoft.Data.SqlTypes/SqlFileStream.xml @@ -18,19 +18,19 @@ The class is derived from the class, which represents an abstraction of a sequence of bytes from some arbitrary data source such as a file or a block of memory. You can read from a FILESTREAM by transferring data from a stream into a data structure such as an array of bytes. You can write to a FILESTREAM by transferring the data from a data structure into a stream. You can also seek within the stream, which allows you to query and modify data at the current position within the stream. - For conceptual documentation and code examples, see FILESTREAM Data. + For conceptual documentation and code examples, see FILESTREAM Data. For documentation about setting up and configuring FILESTREAM data on SQL Server, see Designing and Implementing FILESTREAM Storage in SQL Server 2008 Books Online. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) - + SQL Server Data Type Mappings (ADO.NET) - + SQL Server Binary and Large-Value Data (ADO.NET) @@ -85,7 +85,7 @@ - For more information about CAS, see Code Access Security and ADO.NET. + For more information about CAS, see Code Access Security and ADO.NET. If an exception is thrown, any open transactions should be rolled back. Otherwise, data loss can occur. @@ -120,7 +120,7 @@ NtCreateFile fails with error code set to ERROR_SHARING_VIOLATION. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -170,7 +170,7 @@ - For more information about CAS, see Code Access Security and ADO.NET. + For more information about CAS, see Code Access Security and ADO.NET. If an exception is thrown, any open transactions should be rolled back. Otherwise, data loss can occur. @@ -205,7 +205,7 @@ NtCreateFile fails with error code set to ERROR_SHARING_VIOLATION. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -237,7 +237,7 @@ Reading data is not supported on the stream. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -269,7 +269,7 @@ Writing data is not supported on the stream. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -280,7 +280,7 @@ if the current stream supports reading; otherwise, . - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -291,7 +291,7 @@ if the current stream supports seeking; otherwise, . - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -310,7 +310,7 @@ if the current stream supports writing; otherwise, . - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -343,7 +343,7 @@ The object did not come from the corresponding method. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -357,7 +357,7 @@ The object did not come from the corresponding method. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -370,7 +370,7 @@ Clears all buffers for this stream and causes any buffered data to be written to the underlying device. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -381,7 +381,7 @@ An indicating the length of the current stream in bytes. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -392,7 +392,7 @@ A string value indicating the name of the . - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -403,7 +403,7 @@ The current position within the . - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -429,7 +429,7 @@ The object does not support reading of data. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -446,7 +446,7 @@ The object does not support reading of data. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -457,7 +457,7 @@ A value, in milliseconds, that determines how long the stream will attempt to read before timing out. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -474,7 +474,7 @@ The new position within the current stream. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -491,7 +491,7 @@ The object does not support reading of data. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -502,7 +502,7 @@ The TransactionContext array that was passed to the constructor for this object. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -525,7 +525,7 @@ The object does not support writing of data. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -542,7 +542,7 @@ The object does not support writing of data. - + FILESTREAM Data in SQL Server 2008 (ADO.NET) @@ -553,7 +553,7 @@ A value, in milliseconds, that determines how long the stream will attempt to write before timing out. - + FILESTREAM Data in SQL Server 2008 (ADO.NET)