Fixes a problem where a connection failure is reported when you use the ADO.NET 2.0 SqlConnection object to connect to a database server that is available.

Describes a fix for a problem that occurs when you use the OLE DB Provider for SQL Server to modify a row on a table. If the table contains a trigger, and the trigger contains a FETCH command, you receive an error message.

Explains that you receive a "Cannot start more transactions on this session" error message when you use OLEDBSQL in ADO.NET. Occurs because OLEDBSQL does not allow nested transactions.

Any application can hit performance issues and timeouts while connecting with SQL Server. This fix introduces two new columns, error_code and op_history in sys.dm_os_buffer_descriptors DMV. Error_code column represents the error information during latest attempt to populate the buffer in question.

Assume that you use the SqlLocalDB feature in Microsoft SQL Server 2019 or 2017. In this situation, you can't start correctly or connect to a shared instance of SqlLocalDB. This problem is fixed in the following cumulative updates for SQL Server:

Fixes an issue in which automatic seeding fails when you use an Always On availability group in SQL Server.

Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. This issue occurs because the Windows cluster cannot create and bring online the client access point that is a clustered resource.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem is fixed in the following cumulative updates for SQL Server: About cumulative updates for SQL Server:

To work around the issue, do the following to set the Compatibility Level of the Database to 80: In Enterprise Manager, right click the database. Select Properties. Change the Compatibility Level to 80.

The Microsoft .NET Framework Registration Correction Tool (msipatchregfix.exe) corrects a limited set of Windows Installer (MSI) registration corruption issues for .NET Framework updates.