From d2f372394538bda6c93f6fd01008c76f6b873ce8 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Wed, 8 Aug 2018 17:28:19 -0700 Subject: [PATCH] remove SQL Server Books Online --- xml/Microsoft.SqlServer.Server/SqlContext.xml | 2 +- .../SqlTriggerContext.xml | 2 +- .../TriggerAction.xml | 2 +- xml/System.Data.Common/DbDataAdapter.xml | 10 +- xml/System.Data.SqlClient/SqlBulkCopy.xml | 2 +- xml/System.Data.SqlClient/SqlConnection.xml | 22 ++-- .../SqlConnectionStringBuilder.xml | 4 +- xml/System.Data.SqlClient/SqlDataAdapter.xml | 2 +- xml/System.Data.SqlClient/SqlDataReader.xml | 2 +- xml/System.Data.SqlClient/SqlDependency.xml | 118 ++---------------- xml/System.Data.SqlClient/SqlError.xml | 14 +-- xml/System.Data.SqlClient/SqlException.xml | 8 +- .../SqlNotificationSource.xml | 22 +--- xml/System.Data.SqlClient/SqlTransaction.xml | 16 +-- xml/System.Data.SqlTypes/SqlSingle.xml | 2 +- xml/System.Data/CommandBehavior.xml | 2 +- xml/System.Data/MissingSchemaAction.xml | 2 +- xml/ns-Microsoft.SqlServer.Server.xml | 2 +- 18 files changed, 56 insertions(+), 178 deletions(-) diff --git a/xml/Microsoft.SqlServer.Server/SqlContext.xml b/xml/Microsoft.SqlServer.Server/SqlContext.xml index c518df4e623..ba72201ebe4 100644 --- a/xml/Microsoft.SqlServer.Server/SqlContext.xml +++ b/xml/Microsoft.SqlServer.Server/SqlContext.xml @@ -168,7 +168,7 @@ ## Examples - The following example shows how to get the Windows identity of the calling client and impersonate the client. See "Impersonation Sample" in SQL Server Books Online for an example of impersonation using the property. + The following example shows how to get the Windows identity of the calling client and impersonate the client. [!code-csharp[DataWorks SqlContext.WindowsIdentity Sample#1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/DataWorks SqlContext.WindowsIdentity Sample/CS/source.cs#1)] [!code-vb[DataWorks SqlContext.WindowsIdentity Sample#1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/DataWorks SqlContext.WindowsIdentity Sample/VB/source.vb#1)] diff --git a/xml/Microsoft.SqlServer.Server/SqlTriggerContext.xml b/xml/Microsoft.SqlServer.Server/SqlTriggerContext.xml index 911e65e8622..da53b23f48c 100644 --- a/xml/Microsoft.SqlServer.Server/SqlTriggerContext.xml +++ b/xml/Microsoft.SqlServer.Server/SqlTriggerContext.xml @@ -21,7 +21,7 @@ is available from the class, when the code is running inside a trigger through the property. diff --git a/xml/Microsoft.SqlServer.Server/TriggerAction.xml b/xml/Microsoft.SqlServer.Server/TriggerAction.xml index b08b9008d22..e4476fc9efe 100644 --- a/xml/Microsoft.SqlServer.Server/TriggerAction.xml +++ b/xml/Microsoft.SqlServer.Server/TriggerAction.xml @@ -22,7 +22,7 @@ ## Remarks The enumeration is used by the class to indicate what action fired the trigger. - For more information, see the Transact-SQL Reference of SQL Server Books Online. + For more information, see the [Transact-SQL Reference](/sql/t-sql/language-reference). ]]> diff --git a/xml/System.Data.Common/DbDataAdapter.xml b/xml/System.Data.Common/DbDataAdapter.xml index 69a8adf866a..a07a065ad08 100644 --- a/xml/System.Data.Common/DbDataAdapter.xml +++ b/xml/System.Data.Common/DbDataAdapter.xml @@ -1441,7 +1441,7 @@ adapter.Fill(dataset, "AAA"); // Fills table "aaa" because only one similarly na > [!NOTE] > When handling batch SQL statements that return multiple results, the implementation of for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the set to `AddWithKey`. - When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). @@ -1529,7 +1529,7 @@ adapter.Fill(dataset, "AAA"); // Fills table "aaa" because only one similarly na > [!NOTE] > When handling batch SQL statements that return multiple results, the implementation of for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the set to `AddWithKey`. - When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). @@ -1637,7 +1637,7 @@ adapter.FillSchema(dataset, "AAA"); // Fills the schema of table "aaa" because o > [!NOTE] > When handling batch SQL statements that return multiple results, the implementation of for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the set to `AddWithKey`. - When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). @@ -1728,7 +1728,7 @@ adapter.FillSchema(dataset, "AAA"); // Fills the schema of table "aaa" because o > [!NOTE] > When handling batch SQL statements that return multiple results, the implementation of for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the set to `AddWithKey`. - When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). ]]> @@ -1833,7 +1833,7 @@ adapter.FillSchema(dataset, "AAA"); // Fills the schema of table "aaa" because o > [!NOTE] > When handling batch SQL statements that return multiple results, the implementation of for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the set to `AddWithKey`. - When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). ]]> diff --git a/xml/System.Data.SqlClient/SqlBulkCopy.xml b/xml/System.Data.SqlClient/SqlBulkCopy.xml index 503b1298743..866fad2e3b0 100644 --- a/xml/System.Data.SqlClient/SqlBulkCopy.xml +++ b/xml/System.Data.SqlClient/SqlBulkCopy.xml @@ -511,7 +511,7 @@ If is modified while a operation is running, the change does not affect the current operation. The new value is used the next time a method is called. - is a three-part name (`..`). You can qualify the table name with its database and owning schema if you choose. However, if the table name uses an underscore ("_") or any other special characters, you must escape the name using surrounding brackets as in (`[..]`). For more information, see "Identifiers" in SQL Server Books Online. + is a three-part name (`..`). You can qualify the table name with its database and owning schema if you choose. However, if the table name uses an underscore ("_") or any other special characters, you must escape the name using surrounding brackets as in (`[..]`). For more information, see [Database Identifiers](/sql/relational-databases/databases/database-identifiers). You can bulk-copy data to a temporary table by using a value such as `tempdb..#table` or `tempdb..#table` for the property. diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml index 8f65c04b679..e80d69bdfec 100644 --- a/xml/System.Data.SqlClient/SqlConnection.xml +++ b/xml/System.Data.SqlClient/SqlConnection.xml @@ -80,7 +80,7 @@ using (SqlConnection connection = new SqlConnection(connectionString)) 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)](~/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md) to modify security policy at the machine, user, and enterprise levels. For more information, see [Security in .NET](~/docs//standard/security/index.md). For an example demonstrating how to use security demands, see [Code Access Security and ADO.NET](~/docs/framework/data/adonet/code-access-security.md). - For more information about handling warning and informational messages from the server, see [Connection Events](~/docs/framework/data/adonet/connection-events.md). SQL Server engine errors and error messages are documented in SQL Server Books Online. + For more information about handling warning and informational messages from the server, see [Connection Events](~/docs/framework/data/adonet/connection-events.md). For more information about SQL Server engine errors and error messages, see [Database Engine Events and Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). > [!CAUTION] > 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. @@ -370,7 +370,7 @@ using (SqlConnection connection = new SqlConnection(connectionString)) > [!CAUTION] > When your query returns a large amount of data and calls `BeginTransaction`, 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 "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). @@ -429,9 +429,9 @@ using (SqlConnection connection = new SqlConnection(connectionString)) 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. > [!NOTE] -> 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 [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see "Isolation Levels in the Database Engine" in SQL Server Books Online. +> 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 [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels). - For more information on SQL Server transactions, see "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). > [!CAUTION] > When your query returns a large amount of data and calls `BeginTransaction`, 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. @@ -496,7 +496,7 @@ using (SqlConnection connection = new SqlConnection(connectionString)) You must explicitly commit or roll back the transaction using the or method. To make sure that the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 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 "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). > [!CAUTION] > When your query returns a large amount of data and calls `BeginTransaction`, 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. @@ -562,9 +562,9 @@ using (SqlConnection connection = new SqlConnection(connectionString)) 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. > [!NOTE] -> 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 [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see "Isolation Levels in the Database Engine" in SQL Server Books Online. +> 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 [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call followed immediately by . For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels). - For more information on SQL Server transactions, see "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). > [!CAUTION] > When your query returns a large amount of data and calls `BeginTransaction`, 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. @@ -1727,7 +1727,7 @@ End Module > [!NOTE] > 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](~/docs/framework/data/adonet/connection-events.md). For more information on errors generated by the SQL Server engine, see SQL Server Books Online. + For more information on working with events, see [Connection Events](~/docs/framework/data/adonet/connection-events.md). For more information on errors generated by the SQL Server engine, see [Database Engine Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). ]]> @@ -1745,7 +1745,7 @@ End Module @@ -2129,7 +2129,7 @@ class Program { ## Remarks 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" in SQL Server Books Online. + 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](/sql/relational-databases/errors-events/database-engine-error-severities). For more information and an example, see [Connection Events](~/docs/framework/data/adonet/connection-events.md). @@ -2305,7 +2305,7 @@ class Program { 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 Architecture](http://go.microsoft.com/fwlink/?LinkId=143705) in SQL Server Books Online. + 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](/sql/relational-databases/memory-management-architecture-guide). diff --git a/xml/System.Data.SqlClient/SqlConnectionStringBuilder.xml b/xml/System.Data.SqlClient/SqlConnectionStringBuilder.xml index bb7e9733dcb..3d08c060ada 100644 --- a/xml/System.Data.SqlClient/SqlConnectionStringBuilder.xml +++ b/xml/System.Data.SqlClient/SqlConnectionStringBuilder.xml @@ -2285,7 +2285,7 @@ Database = AdventureWorks ## Remarks When `TrustServerCertificate` is set to `true`, the transport layer will use SSL to encrypt the channel and bypass walking the certificate chain to validate trust. If `TrustServerCertificate` is set to `true` and encryption is turned on, the encryption level specified on the server will be used even if `Encrypt` is set to `false`. The connection will fail otherwise. - For more information, see "Encryption Hierarchy" and "Using Encryption Without Validation" in SQL Server Books Online. + For more information, see [Encryption Hierarchy](/sql/relational-databases/security/encryption/encryption-hierarchy) and [Using Encryption Without Validation](/sql/relational-databases/native-client/features/using-encryption-without-validation). ]]> @@ -2522,7 +2522,7 @@ Unable to retrieve value for null key. This property corresponds to the "User Instance" key within the connection string. > [!NOTE] -> This feature is available only with the SQL Server Express Edition. For more information on user instances, see [SQL Server Express User Instances](~/docs/framework/data/adonet/sql/sql-server-express-user-instances.md) and "User Instances for Non-Administrators" in SQL Server Books Online. +> This feature is available only with the SQL Server Express Edition. For more information on user instances, see [SQL Server Express User Instances](~/docs/framework/data/adonet/sql/sql-server-express-user-instances.md). ]]> diff --git a/xml/System.Data.SqlClient/SqlDataAdapter.xml b/xml/System.Data.SqlClient/SqlDataAdapter.xml index fa777b557a6..ce34e56a14a 100644 --- a/xml/System.Data.SqlClient/SqlDataAdapter.xml +++ b/xml/System.Data.SqlClient/SqlDataAdapter.xml @@ -81,7 +81,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. > [!NOTE] -> 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 [Creating and Using User-Defined Types](http://go.microsoft.com/fwlink/?LinkId=139492) in SQL Server Books Online. +> 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](/sql/relational-databases/clr-integration-database-objects-user-defined-types/clr-user-defined-types). diff --git a/xml/System.Data.SqlClient/SqlDataReader.xml b/xml/System.Data.SqlClient/SqlDataReader.xml index ffae8a5935a..6fa12c05ab5 100644 --- a/xml/System.Data.SqlClient/SqlDataReader.xml +++ b/xml/System.Data.SqlClient/SqlDataReader.xml @@ -1506,7 +1506,7 @@ |BaseTableName|The name of the table or view in the data store that contains the column. A null value if the base table name cannot be determined. The default of this column is a null value.| |ColumnName|The name of the column; this might not be unique. If this cannot be determined, a null value is returned. This name always reflects the most recent renaming of the column in the current view or command text.| |ColumnOrdinal|The zero-based ordinal of the column. This column cannot contain a null value.| -|ColumnSize|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 in SQL Server Books Online.| +|ColumnSize|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](/sql/t-sql/language-reference).| |DataTypeName|Returns a string representing the data type of the specified column.| |IsAliased|`true`: The column name is an alias.

`false`: The column name is not an alias.| |IsAutoIncrement|`true`: The column assigns values to new rows in fixed increments.

`false`: The column does not assign values to new rows in fixed increments. The default of this column is `false`.| diff --git a/xml/System.Data.SqlClient/SqlDependency.xml b/xml/System.Data.SqlClient/SqlDependency.xml index 1e8c2811eaa..adbc5956a74 100644 --- a/xml/System.Data.SqlClient/SqlDependency.xml +++ b/xml/System.Data.SqlClient/SqlDependency.xml @@ -23,37 +23,17 @@ ## Remarks 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 "Creating a Query for Notification" in SQL Server Books Online. + 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](/sql/relational-databases/native-client/features/working-with-query-notifications). > [!NOTE] -> 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 Efficient Query Notifications Strategy** and **Alternatives to Query Notifications** in the [Planning for Notifications](http://go.microsoft.com/fwlink/?LinkId=211984) topic in SQL Server Books Online. +> 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 Efficient Query Notifications Strategy](https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms187528(v=sql.105)#planning-an-efficient-query-notifications-strategy) and [Alternatives to Query Notifications](https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms187528(v=sql.105)#alternatives-to-query-notifications) in the [Planning for Notifications](https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms187528(v%3dsql.105)) article. - For more information, see [Query Notifications in SQL Server](~/docs/framework/data/adonet/sql/query-notifications-in-sql-server.md) and "Building Notification Solutions" in SQL Server Books Online. + For more information, see [Query Notifications in SQL Server](~/docs/framework/data/adonet/sql/query-notifications-in-sql-server.md) and [Building Notification Solutions](https://docs.microsoft.com/previous-versions/sql/sql-server-2005/ms171065(v%3dsql.90)). > [!NOTE] > The event may be generated on a different thread from the thread that initiated command execution. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. The following table provides links to the Service Broker and Query Notifications documentation in SQL Server Books Online. - - **SQL Server Books Online** - -- [Creating a Query for Notification](http://msdn.microsoft.com/library/ms181122.aspx) - -- [Security Considerations for Service Broker](http://msdn.microsoft.com/library/ms166059.aspx) - -- [Security and Protection (Service Broker)](http://msdn.microsoft.com/library/bb522911.aspx) - -- [Security Considerations for Notifications Services](http://msdn.microsoft.com/library/ms172604.aspx) - -- [Query Notification Permissions](http://msdn.microsoft.com/library/ms188311.aspx) - -- [International Considerations for Service Broker](http://msdn.microsoft.com/library/ms166028.aspx) - -- [Solution Design Considerations (Service Broker)](http://msdn.microsoft.com/library/bb522899.aspx) - -- [Service Broker Developer InfoCenter](http://msdn.microsoft.com/library/ms166100.aspx) - -- [Developer's Guide (Service Broker)](http://msdn.microsoft.com/library/bb522908.aspx) + Query notifications are supported only for SELECT statements that meet a list of specific requirements. ]]> @@ -91,28 +71,8 @@ ## Remarks 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. The following table provides links to the Service Broker and Query Notifications documentation in SQL Server Books Online. - - **SQL Server Books Online** - -- [Creating a Query for Notification](http://msdn.microsoft.com/library/ms181122.aspx) - -- [Security Considerations for Service Broker](http://msdn.microsoft.com/library/ms166059.aspx) - -- [Security and Protection (Service Broker)](http://msdn.microsoft.com/library/bb522911.aspx) - -- [Security Considerations for Notifications Services](http://msdn.microsoft.com/library/ms172604.aspx) - -- [Query Notification Permissions](http://msdn.microsoft.com/library/ms188311.aspx) - -- [International Considerations for Service Broker](http://msdn.microsoft.com/library/ms166028.aspx) - -- [Solution Design Considerations (Service Broker)](http://msdn.microsoft.com/library/bb522899.aspx) - -- [Service Broker Developer InfoCenter](http://msdn.microsoft.com/library/ms166100.aspx) - -- [Developer's Guide (Service Broker)](http://msdn.microsoft.com/library/bb522908.aspx) - + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see [SQL Server Service Broker](/sql/database-engine/configure-windows/sql-server-service-broker) and [Working with Query Notifications](/sql/connect/oledb/features/working-with-query-notifications). + ]]> @@ -143,27 +103,7 @@ ## Remarks 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. The following table provides links to the Service Broker and Query Notifications documentation in SQL Server Books Online. - - **SQL Server Books Online** - -- [Creating a Query for Notification](http://msdn.microsoft.com/library/ms181122.aspx) - -- [Security Considerations for Service Broker](http://msdn.microsoft.com/library/ms166059.aspx) - -- [Security and Protection (Service Broker)](http://msdn.microsoft.com/library/bb522911.aspx) - -- [Security Considerations for Notifications Services](http://msdn.microsoft.com/library/ms172604.aspx) - -- [Query Notification Permissions](http://msdn.microsoft.com/library/ms188311.aspx) - -- [International Considerations for Service Broker](http://msdn.microsoft.com/library/ms166028.aspx) - -- [Solution Design Considerations (Service Broker)](http://msdn.microsoft.com/library/bb522899.aspx) - -- [Service Broker Developer InfoCenter](http://msdn.microsoft.com/library/ms166100.aspx) - -- [Developer's Guide (Service Broker)](http://msdn.microsoft.com/library/bb522908.aspx) + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see [SQL Server Service Broker](/sql/database-engine/configure-windows/sql-server-service-broker) and [Working with Query Notifications](/sql/connect/oledb/features/working-with-query-notifications). ]]> @@ -199,27 +139,7 @@ @@ -257,27 +177,7 @@ diff --git a/xml/System.Data.SqlClient/SqlError.xml b/xml/System.Data.SqlClient/SqlError.xml index 6de5081b99d..9b31b551571 100644 --- a/xml/System.Data.SqlClient/SqlError.xml +++ b/xml/System.Data.SqlClient/SqlError.xml @@ -91,7 +91,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 SQL Server Books Online. + For more information on errors generated by SQL Server, see [Database Engine Events and Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). @@ -141,7 +141,7 @@ ## Remarks 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 SQL Server Books Online. + For more information on errors generated by SQL Server, see [Database Engine Events and Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). @@ -184,9 +184,7 @@ Gets the text describing the error. - The text describing the error. - - For more information on errors generated by SQL Server, see SQL Server Books Online. + The text describing the error. For more information on errors generated by SQL Server, see Database Engine Events and Errors. 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 SQL Server Books Online. + The name of the stored procedure or RPC. For more information on errors generated by SQL Server, see Database Engine Events and Errors. 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 the Troubleshooting section of SQL Server Books Online. 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](/sql/relational-databases/errors-events/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 System.Transaction.TransactionScope or the BeginTransaction method (in System.Data.OleDb.OleDbConnection, System.Data.ODBC.ODBCConnection, and System.Data.SqlClient.SqlConnection) ensure consistent data regardless of exceptions raised by a provider. Transactions can fail, so catch failures and retry the transaction. @@ -240,7 +240,7 @@ catch (Exception ex) { ## Remarks 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 SQL Server Books Online. + This is a wrapper for . For more information on SQL Server engine errors, see [Database Engine Events and Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). @@ -410,7 +410,7 @@ catch (Exception ex) { property of the first in the property. For more information on SQL Server engine errors, see SQL Server Books Online. + This is a wrapper for the property of the first in the property. For more information on SQL Server engine errors, see [Database Engine Events and Errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). @@ -620,7 +620,7 @@ catch (Exception ex) { System.Byte - 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 SQL Server Books Online. + 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. class. - Query notifications are supported only for SELECT statements that meet a list of specific requirements. The following table provides links to the Service Broker and Query Notifications documentation in SQL Server Books Online. - - **SQL Server Books Online** - -- [Creating a Query for Notification](http://msdn.microsoft.com/library/ms181122.aspx) - -- [Security Considerations for Service Broker](http://msdn.microsoft.com/library/ms166059.aspx) - -- [Security and Protection (Service Broker)](http://msdn.microsoft.com/library/bb522911.aspx) - -- [Security Considerations for Notifications Services](http://msdn.microsoft.com/library/ms172604.aspx) - -- [Query Notification Permissions](http://msdn.microsoft.com/library/ms188311.aspx) - -- [International Considerations for Service Broker](http://msdn.microsoft.com/library/ms166028.aspx) - -- [Solution Design Considerations (Service Broker)](http://msdn.microsoft.com/library/bb522899.aspx) - -- [Service Broker Developer InfoCenter](http://msdn.microsoft.com/library/ms166100.aspx) - -- [Developer's Guide (Service Broker)](http://msdn.microsoft.com/library/bb522908.aspx) + Query notifications are supported only for SELECT statements that meet a list of specific requirements. For more information, see [SQL Server Service Broker](/sql/database-engine/configure-windows/sql-server-service-broker) and [Working with Query Notifications](/sql/connect/oledb/features/working-with-query-notifications). ]]> diff --git a/xml/System.Data.SqlClient/SqlTransaction.xml b/xml/System.Data.SqlClient/SqlTransaction.xml index 3b34e6ba6cd..6a8b545c184 100644 --- a/xml/System.Data.SqlClient/SqlTransaction.xml +++ b/xml/System.Data.SqlClient/SqlTransaction.xml @@ -92,12 +92,13 @@ 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 SQL Server Books Online. + 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) +](/sql/t-sql/language-elements/commit-transaction-transact-sql). > [!NOTE] > `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 "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). @@ -287,7 +288,7 @@ ## Remarks Parallel transactions are not supported. Therefore, the applies to the whole transaction. - For more information on SQL Server isolation levels, see "Isolation Levels in the Database Engine" in SQL Server Books Online. + For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels). ]]> @@ -340,14 +341,15 @@ method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see SQL Server Books Online. + The method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see [ROLLBACK TRANSACTION (Transact-SQL) +](/sql/t-sql/language-elements/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 `Commit` or `Rollback` is called. > [!NOTE] > `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 "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). @@ -404,14 +406,14 @@ method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see "Explicit Transactions" and "Transaction Savepoints" in SQL Server Books Online. + The method is equivalent to the Transact-SQL ROLLBACK TRANSACTION statement. For more information, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/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 `Commit` or `Rollback` is called. > [!NOTE] > `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 "Explicit Transactions" and "Coding Efficient Transactions" in SQL Server Books Online. + For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql). diff --git a/xml/System.Data.SqlTypes/SqlSingle.xml b/xml/System.Data.SqlTypes/SqlSingle.xml index a1ef19705f2..ccb2697e86d 100644 --- a/xml/System.Data.SqlTypes/SqlSingle.xml +++ b/xml/System.Data.SqlTypes/SqlSingle.xml @@ -50,7 +50,7 @@ or SQL Server Books Online. + Maps to the SQL Server real data type. For more information, see . ]]> diff --git a/xml/System.Data/CommandBehavior.xml b/xml/System.Data/CommandBehavior.xml index 2f0c75f583b..137aee474d1 100644 --- a/xml/System.Data/CommandBehavior.xml +++ b/xml/System.Data/CommandBehavior.xml @@ -152,7 +152,7 @@ ## Remarks When KeyInfo is used for command execution, the provider will append extra columns to the result set for existing primary key and timestamp columns. - When using KeyInfo, the .NET Framework Data Provider for SQL Server precedes the statement being executed with SET FMTONLY OFF and SET NO_BROWSETABLE ON. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + When using KeyInfo, the .NET Framework Data Provider for SQL Server precedes the statement being executed with SET FMTONLY OFF and SET NO_BROWSETABLE ON. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see [SET FMTONLY (Transact-SQL)](/sql/t-sql/statements/set-fmtonly-transact-sql). ]]> diff --git a/xml/System.Data/MissingSchemaAction.xml b/xml/System.Data/MissingSchemaAction.xml index 4589d4c6664..3eb1ba02ec2 100644 --- a/xml/System.Data/MissingSchemaAction.xml +++ b/xml/System.Data/MissingSchemaAction.xml @@ -98,7 +98,7 @@ 4 - Adds the necessary columns and primary key information to complete the schema. For more information about how primary key information is added to a , see .To function properly with the .NET Framework Data Provider for OLE DB, requires that the native OLE DB provider obtains necessary primary key information by setting the DBPROP_UNIQUEROWS property, and then determines which columns are primary key columns by examining DBCOLUMN_KEYCOLUMN in the IColumnsRowset. As an alternative, the user may explicitly set the primary key constraints on each . This ensures that incoming records that match existing records are updated instead of appended. When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. See SQL Server Books Online for more information. + Adds the necessary columns and primary key information to complete the schema. For more information about how primary key information is added to a , see .To function properly with the .NET Framework Data Provider for OLE DB, requires that the native OLE DB provider obtains necessary primary key information by setting the DBPROP_UNIQUEROWS property, and then determines which columns are primary key columns by examining DBCOLUMN_KEYCOLUMN in the IColumnsRowset. As an alternative, the user may explicitly set the primary key constraints on each . This ensures that incoming records that match existing records are updated instead of appended. When using , the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see SET FMTONLY (Transact-SQL). diff --git a/xml/ns-Microsoft.SqlServer.Server.xml b/xml/ns-Microsoft.SqlServer.Server.xml index 31e5fef3e83..557cca64794 100644 --- a/xml/ns-Microsoft.SqlServer.Server.xml +++ b/xml/ns-Microsoft.SqlServer.Server.xml @@ -11,7 +11,7 @@ The class provides a object, through which results are returned to the client from a stored procedure, a object, which provides information about the operation that caused a trigger to be fired, and a object, which can be used to determine the identity of the calling client when the client used integrated security for authentication. - For more information about SQL Server CLR integration and the APIs in the namespace, see SQL Server Books Online. + For more information about SQL Server CLR integration and the APIs in the namespace, see [SQL Server Documentation](/sql/sql-server/). ]]>