7 SQLSERVER

============================================================================= Simba SQL Server ODBC Driver Release Notes =============================================================================

The release notes provide details of enhancements, features, and known issues in Simba SQL Server ODBC Driver 1.3.13, as well as the version history.

1.3.13 =======================================================================

Released 2017-09-27

Enhancements & New Features

  • Prefixes for log file names

    You can now configure the driver to add a prefix to log file names. The prefix includes the user name associated with the connection and the process ID of the application through which the connection is made. To enable this feature, set the UseLogPrefix connection property to 1. For more information, see the Installation and Configuration Guide.

Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.

  • The SQL_VARIANT data type is not supported.

    The driver exposes the SQL_VARIANT data type as SQL data type -150.

  • The installer for the macOS version of the driver does not alert the user when it fails to write to odbcinst.ini.

    When the installer fails to write to the odbcinst.ini configuration file, instead of alerting you of the error, the installer reports the event in a log file.

Version History ==============================================================

1.3.12 ———————————————————————–

Released 2017-08-25

Enhancements & New Features

  • Retrieval of temporary tables

    You can now configure the driver to include temporary tables in the results when calling SQLTable. To do this, enable the “Enable Table Types” option (the EnableTableTypes property).

  • Driver now supports 1/0 and true/false as values for Boolean connection properties

    When configuring Boolean properties in a connection string or in the odbc.ini file, you can now enable these properties by specifying “yes”, “1”, or “true”; conversely, you can disable these properties by specifying “no”, “0”, or “false”. Previously, the driver only supported “yes” and “no” as values.

    Boolean connection properties include the following:
    • EnableTableTypes
    • Encrypt
    • ReturnSpecificTypeAsOdbcType
    • TrustServerCertificate
    • Trusted_Connection / Integrated Security

Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Driver 1.3.12.

  • When a connection failure occurs, the driver returns an error message with the wrong SQL state.

    This issue has been resolved. The driver now returns SQL state 08S01 instead of 00000.

1.3.11 ———————————————————————–

Released 2017-06-12

Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Driver 1.3.11.

  • If ReturnSpecificTypeAsOdbcType is set to Yes, an access violation occurs after a SQLFetch operation.

1.3.10 ———————————————————————–

Released 2017-06-02

Enhancements & New Features

  • Use ODBC data types

    The driver can be configured to return ODBC data types instead of certain SQL Server-specific data types such as TDS_SQL_SS_TIME and TDS_SQL_SS_ DATETIMEOFFSET. To return ODBC data types, select the Return SQL Server- Specific Types As ODBC Types check box, or set the ReturnSpecificTypeAsOdbcType property to “yes”.

  • Return SQLState 08S01 when existing connection cannot be used

    The driver now returns SQLState 08S01 if for any reason the client cannot use the existing connection to communicate with the driver. Previously the driver incorrectly returned SQLState HY000 in some situations.

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.10.

  • If odbcinst.ini already has entries, an entry is not added for the driver.

  • Data conversion error occurs when converting from C data types to SQL_CHAR.

  • Error occurs when converting from SQL to C numeric types.

  • Error messages do not have the driver branding information appended to them.

1.3.9 ————————————————————————

Released 2017-04-03

Enhancements & New Features

  • TLS Support

    The driver now supports TLS 1.2. The driver automatically detects the highest TLS version the server supports and uses this version when negotiating the connection.

1.3.8 ————————————————————————

Released 2017-03-15

Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Driver 1.3.8.

  • In some cases, when the driver executes parameterized queries, a memory leak occurs.

1.3.7 ————————————————————————

Released 2016-11-15

Enhancements & New Features

  • Improved error code handling

    When a connection fails the driver now returns the specific SQLSTATE information, instead of general system message.

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.7.

  • Stored procedures executed as prepared statements with parameters now return result sets correctly.

  • DBCC SHOW_STATISTICS query returns data correctly when executed as a prepared statement with parameters.

  • When re-executing prepared statements with VARCHAR(MAX) or NVARCHAR(MAX) columns, the driver would stop responding.

1.3.6 ————————————————————————

Released 2016-08-31

Enhancements & New Features

  • Improved error code handling.

    The driver no longer returns only General Error ‘HY000’, but will instead report the SQL state. Also the driver will now report the first native error code rather than the last native error code returned by the server.

  • Log file creation

    User names appearing in log files will now be obscured.

Resolved Issues The following issues were resolved in Simba SQL Server ODBC Driver 1.3.6.

  • When making a connection with SQLDriverConnect if you did not specify all the settings correctly, the required DSN box would be greyed-out and you could not proceed.

1.3.5 ————————————————————————

Released 2016-07-26

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.5.

  • If an SSL connection fails multiple times, the driver reports a different error message for the first attempt compared to all subsequent attempts.

    The driver now consistently reports the correct error message.

  • When using a parameter with SQL_DATA_AT_EXEC to insert data into an NText column, the driver returns an error.

1.3.4 ————————————————————————

Released 2016-07-06

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.4.

  • NCHAR, NVARCHAR, NTEXT data truncated incorrectly.

  • ICU conversion errors.

1.3.3 ————————————————————————

Released 2016-06-24

Enhancements & New Features

  • Updated error codes

    Previously, when reporting errors, the driver used error codes and messages that were native to Simba software. The driver now uses the same error codes and messages as SQL Server, simplifying the process of identifying and resolving errors. The driver has also been updated to use 0 as the default error code.

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.3.

  • Driver crashes when retrieving more than one zero from a NUMERIC type column.

  • Driver returns results from NUMERIC column with extra zeros on the right side when scale is not set to zero.

  • Driver unable to return values for MONEY type columns.

1.3.2 ————————————————————————

Released 2016-05-12

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.2.

  • Driver handles data of type TINYINT as signed data.

    In SQL Server, TINYINT data is unsigned. The driver now handles TINYINT data as unsigned data for compatibility with SQL Server.

1.3.1 ————————————————————————

Released 2016-04-11

Enhancements & New Features

  • HierarchyID and DateTimeOffset are now supported

    The driver now supports HierarchyID and DateTimeOffset types.

  • LOB types are now supported without truncation

    The driver now supports LOB types that do not specify a length. Length limits can still be set to truncate the data at the specified length.

  • varchar(max) and varbinary(max) parameters bound with a column length of 0 do not take their data length from the source data

    The Simba Microsoft SQL Server ODBC Driver now treats varchar(max) and varbinary(max) parameters the same way as the native SQL Server driver.

  • Additional data type support for parameterized queries

    The following data types can now be used with parameters:
    • DateTimeOffset
    • Geography
    • Geometry
    • SQL_LONGVARBINARY
    • SQL_LONGVARCHAR
    • SQL_WLONGVARCHAR
    • Time
    • XML

  • Additional parameter support

    Output and return parameters, and Data-At-Exec input parameters, are now supported.

  • Updated handling of data retrieval

    You can now retrieve columns from a result set in any order. Previously, columns had to be retrieved in sequential order.

Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.3.1.

  • Parameters used as arguments for T-SQL scalar functions do not report their metadata correctly at prepare.

  • Stored procedures should be reported as returning returning row counts instead of result sets when relevant.

  • Crash when tracing is enabled and a DateTimeOffset is retrieved with a negative year.

  • When using array binding in variable length parameters, if a longer value is bound after a shorter value, the driver truncates the longer value.

  • When using Unicode characters in NChar type parameters, the driver does not execute the statement correctly.

==============================================================================