Mimer SQL Data Provider help 11.0
Corrected Problems
Mimer SQL Data Provider > Overview > Release Notes > Corrected Problems

Corrected functions in Mimer SQL Data Provider (11.0.1B):

  1. The Mimer SQL Monitor is now placed in the correct directory to be able to find the provider DLLs.
  2. The nuget packages are now signed properly.
  3. Distributed transaction handling can now properly handle parallel connections toward a single database server. Previously error code that the transaction id, XID, could not be found was returned.

Corrected functions in Mimer SQL Data Provider (11.0.1A):

  1. When reading large results set from server in an auto-committed transaction each set of rows (eg. 10-200 rows) was executed in its own transaction. I.e. it would be possible to see changes from later transactions in the subsequence sets read from the server. Now a query is executed in one auto-committed transaction.

Corrected functions in Mimer SQL Data Provider (10.1.2A):

  1. When converting from an invalid floating point value, i.e. NAN (Not A Number), the error handling now gives ArgumentOutOfRange exception.
  2. All assemblies are now signed with both SHA1 and SHA2 digital signatures.

Corrected functions in Mimer SQL Data Provider and (10.1.1A):

  1. Handshake communication is now synchronized internally during MimerConnection.Open.
  2. Error handling during handshake processing is updated so that error codes are preserved properly.

Corrected functions in Mimer SQL Data Provider and (10.1.0C):

  1. Comments are now supported in the DbProviderSection of machine.config.

Corrected functions in Mimer SQL Data Provider and (10.1.0B):

  1. The MimerConnectionStringBuilder.Remove method did not correctly remove the requested item. This had strange effects on the connection dialog used by the Visual Studio server explorer. This is now corrected along with proper return code for the operation.
  2. No registry entries are now stored under compact framework registry keys.
  3. Uninstallation of the Mimer SQL Data Provider now leaves the registry in a consistent state.
  4. It is now possible to first install Mimer SQL Data Provider, then Visual Studio, followed by a repair of Mimer SQL Data Provider. The repair will correctly register the data provider with Visual Studio 2010.

Corrected functions in Mimer SQL Data Provider and (10.1.0A):

  1. An internal lock is now taken by the MimerConnection class when releasing statement handles in the server. This secures the case where a parallel dispose is made by the garbage collector. This could cause the same statement to be incorrectly freed twice.
  2. When auto-commit is used with read cursor the transaction was not always terminated properly when MimerDataReader.Close was called. This occurred in cases where the last call to the server did not return zero rows or when there were large objects present in the result set.
  3. When connecting to an old Mimer SQL server (i.e. 9.2) the handshake processing did not handle the connection properly resulting in a "server is closed" error message. This has now been corrected.
  4. When installing on a machine without Visual Studio accessing the documentation previously caused a repair of the installation. This will no longer occur.