Mimer SQL Data Provider
Changed Functions
Mimer SQL Data Provider > Overview > Release Notes > Changed Functions

Changed functions in Mimer SQL Data Provider 11.0.4.15 (11.0.4A):

  1. Integration with Visual Studio 2017 is no longer supported. The data providers can still, of course, be used with this version of Visual Studio.
  2. Serializing a MimerException with calling GetObjectData is deprecated in the .NET 8 Mimer SQL Data Provider, as System.Exception.GetObjectData is deprecated in .NET 8.
  3. Some Mimer SQL Data Provider versions are no longer included as they are out of support from Microsoft. This means that the Mimer SQL Data Provider for any .NET Framework version earlier than 4.6.2, for .NET Core, and for any .NET version earlier than 6 has been removed.

Changed functions in Mimer SQL Data Provider 11.0.3.44 (11.0.3D):

  1. MimerTrace is now configured from the local application data folder instead of the roaming application data folder. For information on the exact location, see chapter How to enable trace.
  2. The application data folder for the MimerTrace configuration is no longer created by the trace system, it has to be created manually or by the Mimer SQL Data Provider Trace Control tool.
  3. When a trace file listener is activated, the trace system tries to create both the specified folder and the file if they do not exist. Previously only the file was created by the trace system. If the application does not have write access to the location, nothing will be traced to the file.

Changed functions in Mimer SQL Data Provider 11.0.3.14 (11.0.3A):

  1. Integration with Visual Studio 2013 and Visual Studio 2015 is no longer supported. The data providers can still, of course, be used with these versions of Visual Studio.

Changed functions in Mimer SQL Data Provider 11.0.2.14 (11.0.2A):

  1. In this version distributed transaction handling is no longer supported. This feature was present in the beta version 11.0.1B. However, the required support from .NET is not present in .NET Core and not in .NET 5. This functionality may be reintroduced in a later version.
  2. For the same reason the MimerDtcRecovery executable has been removed from the distribution.

Changed functions in Mimer SQL Data Provider 11.0.1.24 (11.0.1B):

These changes align Mimer SQL ADO.NET with other providers in behavior.

  1. MimerCommand.CommandText now returns an empty string even if it is set to null.
  2. MimerCommand.Cancel allowed even if there is no connection. In this case nothing happens.
  3. For SQL statements that have no row count the return value from MimerCommand.ExecuteNonQuery is now -1 whereas it was 0 before.
  4. Improved error handling for conversion errors from string in the database to double precision. Invalid string arguments now give InvalidcastException.

Changed functions in Mimer SQL Data Provider 11.0.1.14 (11.0.1A):

  1. Buffer sizes doubled in the Mimer SQL server, e.g. 2K buffers are now 4K in size. Therefore names of some performance counters have changed to better reflect this. The term Small is used for 2K, Medium for 16K, and Large instead of 64K. So, for example MimerPerformanceCounters.Pages2k is now named MimerPerformanceCounters.PagesSmall, etc. All the old names are still available for compatibility reasons.
  2. When using double and single precision float in the Mimer SQL version 11 server these now use IEEE-format. This means that the precision matches exactly what is used in .NET and thus, now, gives precise results for these data types when stored and retrieved from the database server.
  3. Integration with Visual Studio 2010 and Visual Studio 2012 no longer supported. The data providers can still, of course, be used with these versions of Visual Studio.

Changed functions in Mimer SQL Data Provider 10.1.2.14 (10.1.2A):

  1. New installer technology used for installation. WIX is used instead of Visual Studio Deployment projects.

Changed functions in Mimer SQL Data Provider 10.1.0.32 and 10.1.0.34 (10.1.0C):

  1. List returned by MimerConnection.GetSchema("ReservedWords") updated with reserved words in version 10.1 of Mimer SQL.

Changed functions in Mimer SQL Data Provider 10.1.0.12 and 10.1.0.14 (10.0.1A):

  1. The column IsUnique and IsKey in the result set returned by MimerDataReader.GetSchemaTable has a slightly different meaning. IsUnique is now true if the single column is unique by itself. IsKey is true if the column is part of a unique key, unique index, or a primary key consisting of one (IsUnique is also true in this case) or several columns.