14 SQLSERVER
============================================================================== Magnitude Simba SQL Server ODBC Data Connector Release Notes ==============================================================================
The release notes provide details of enhancements, features, known issues, and workflow changes in Simba SQL Server ODBC Connector 1.5.13, as well as the version history.
1.5.13 =======================================================================
Released 2022-12-16
Enhancements & New Features
Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Connector 1.5.13.
[MSSQL-887] On RStudio, when executing a stored procedure, the connector returns a “Invalid Cursor State” error.
[MSSQL-884] On macOS, the SQL Server ODBC connector installer does not populate odbcinst.ini.
[MSSQL-885][MSSQL-900] On RStudio, when connecting to SQL Server with application_intent=‘readonly’, the connector displays a 5701 warning instead of the actual error.
Known Issues The following are known issues that you may encounter due to limitations in the data source, the connector, or an application.
[MSSQL-753] When applications run a query on local temporary tables with Prepare and Execute, the connector returns an error.
This is a limitation of SQL Server. Prepared statement execution on local temporary tables is not supported. As a workaround, applications should call SQLExecDirect when working with local temporary tables.
The SQL_VARIANT data type is not supported.
The connector exposes the SQL_VARIANT data type as SQL data type -150.
The installer for the macOS version of the connector 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.
Workflow Changes =============================================================
The following changes may disrupt established workflows for the connector.
1.5.8 ————————————————————————
[MSSQL-723][MSSQL-853] Removed support for earlier versions of operating systems
Beginning with this release, the connector no longer supports the following operating systems:
- RedHat Enterprise Linux (RHEL) 6
- CentOS 6
- Ubuntu 14
For information about supported operating systems, see the Installation and Configuration Guide.
1.5.5 ————————————————————————
[MSSQL-722][MSSQL-783] Removed support for earlier versions of operating systems
Beginning with this release, the connector no longer supports the following operating systems:
- Windows 7 SP1
- Windows Server 2008 R2 SP1
- macOS 10.12 “Sierra”
- SLES 11
- Debian 8
For information about supported operating systems, see the Installation and Configuration Guide.
1.5.1 ————————————————————————
SSL 3.0 is no longer supported
Beginning with this release, the connector does not support SSL 3.0. For information about the supported SSL/TLS versions and instructions for configuring encryption, see the Installation and Configuration Guide.
1.5.0 ————————————————————————
Microsoft SQL Server 2008 and 2008r2 no longer supported
Beginning with this release, the connector does not support SQL Server 2008 and 2008r2. For information about the supported SQL Server versions, see the Installation and Configuration Guide.
1.4.11 ———————————————————————–
Microsoft SQL Server 2005 no longer supported
Beginning with this release, the connector does not support SQL Server 2005. For information about the supported SQL Server versions, see the Installation and Configuration Guide.
1.4.7 ————————————————————————
Minimum TLS Version
Beginning with this release, the connector requires a minimum version of TLS for encrypting the data store connection. By default, the connector requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to datastores that use a TLS version earlier than 1.2.
To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide.
Version History ==============================================================
1.5.10 ———————————————————————–
Released 2021-10-30
Enhancements & New Features
Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Connector 1.5.10.
- [MSSQL-875] In some cases, when inserting data into a text column, the connector becomes unresponsive.
1.5.9 ————————————————————————
Released 2021-06-30
Enhancements & New Features
[MSSQL-694] Updated GCC support
The connector now supports GCC version 4.4.
[MSSQL-871] Updated OpenSSL version
The connector now uses OpenSSL version 1.1.1k. Previously, the connector used OpenSSL version 1.1.1i.
Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Connector 1.5.9.
- [MSSQL-864] In some cases, a rounding issue causes the connector to produce unexpected results for numeric fields.
1.5.8 ————————————————————————
Released 2021-04-30
Enhancements & New Features
[MSSQL-747] Support for NTLMv2
On Unix systems, you can now authenticate the connection using NT Lan Manager version 2 (NTLMv2). To do this, set the Trusted_Connection property to NTLMv2. 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 connector, or an application.
[MSSQL-753] When applications run a query on local temporary tables with Prepare and Execute, the connector returns an error.
This is a limitation of SQL Server. Prepared statement execution on local temporary tables is not supported. As a workaround, applications should call SQLExecDirect when working with local temporary tables.
The SQL_VARIANT data type is not supported.
The connector exposes the SQL_VARIANT data type as SQL data type -150.
The installer for the macOS version of the connector 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.
1.5.6 ————————————————————————
Released 2021-03-30
Enhancements & New Features
[MSSQL-846] Support for APP keyword
You can now specify the APP keyword, which SQL Server uses to indicate the name of the application that calls SQLDriverConnect. To do this, in the Application Name field (the Application_Name configuration property), specify the name of the application. For more information, see the Installation and Configuration Guide.
[MSSQL-825] Updated metadata for SQL_DECIMAL
The metadata for SQL_DECIMAL columns has been updated. Now, the function SQLColAttribute(SQL_DESC_OCTET_LENGTH/SQL_COLUMN_LENGTH) returns (max precision + 2) and the function SQLColAttribute(SQL_DESC_DISPLAY_SIZE) returns at least (max precision + 2), since SQL_DECIMAL supports the maximum precision rather than the specified precision.
Upgraded third-party libraries
The connector has been updated to use the following libraries:
- OpenSSL version 1.1.1i (previously 1.1.1g)
- ICU version 58.3.x (previously 58.2.x)
1.5.5 ————————————————————————
Released 2020-09-30
Enhancements & New Features
[MSSQL-799] Updated logging configurations
You can now configure logging for the current connection by setting the logging configuration properties in the DSN or in a connection string. For more information, see the Installation and Configuration Guide.
[MSSQL-807] Custom maximum name lengths
You can now customize the maximum length of the names of catalogs, columns, schemas, and tables. To do this, set the lengths using the connection properties MaxCatalogNameLen, MaxColumnNameLen, MaxSchemaNameLen, and MaxTableNameLen. For more information, see the Installation and Configuration Guide.
[MSSQL-808] Standardized log file names
When logging is enabled, the driver now produces the following log files:
- A simbasqlserverodbcdriver.log file that logs driver activity that is not specific to a connection.
- A simbasqlserverodbcdriver_connection_[Number].log file for each connection made to the database, where [Number] is a number that identifies each log file. This file logs driver activity that is specific to the connection.
[MSSQL-701] Updated SQL Server support
The driver now supports SQL Server 2019.
[MSSQL-800] Updated OpenSSL version
The driver now uses OpenSSL version 1.1.1g. Previously, the driver used OpenSSL version 1.1.1d.
Resolved Issues The following issue has been resolved in Simba SQL Server ODBC Driver 1.5.5.
[MSSQL-762] When using SQL Server 2012 or 2014 on macOS, the connection fails.
This issue has been resolved. The Min_TLS default value is now set to 1.2 when encryption is requested, and to 1.0 when encryption is not requested. For more information, see the Installation and Configuration Guide.
1.5.4 ————————————————————————
Released 2020-07-30
Enhancements & New Features
[MSSQL-755][MSSQL-768] Specify application intent
You can now configure the driver to specify the application intent. To do this, from the Application Intent drop-down list, select ReadOnly (set the Application_Intent property to ReadOnly). For more information, see the Installation and Configuration Guide.
Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.5.4.
[MSSQL-752] When querying the value of SQL_DESC_AUTO_UNIQUE_VALUE using SQLColAttribute, the driver returns an error.
[MSSQL-761] When driver logging is enabled with LogLevel=6, LogPath is set to a path, and you do not have permission to write to the log file, the connection fails and the driver returns an ambiguous error message.
This has been resolved. The connection now succeeds and the log is written to stdout.
1.5.2 ————————————————————————
Released 2020-03-27
Enhancements & New Features
[MSSQL-724] Support for additional systems
The driver now supports the following operating systems:
- Windows Server 2019
- macOS 10.15
- RHEL 8
- CentOS 8
- SLES 15
The driver now supports the following database management systems:
- SQL Server 2016 & 2017
[MSSQL-712] Upgrade Expat to 2.2.9
The driver now uses Expat 2.2.9 for XML parsing. Previously, the driver used Expat 2.2.7.
Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.5.2.
[MSSQL-708][MSSQL-719] In some cases, when connecting to SQL Server 2016 or 2017, the connection fails and the message “Problem establishing connection to the server” is displayed.
[MSSQL-725] In some cases, when connecting to a database that uses a Thai collation such as Thai_CI_AS, the driver does not display any tables.
1.5.1 ————————————————————————
Released 2019-12-27
Enhancements & New Features
[MSSQL-614] Upgrade to OpenSSL 1.1.1d
The driver now uses OpenSSL 1.1.1d for encryption of data. Previously, the driver used OpenSSL 1.1.0j.
[MSSQL-706] Additional supported key names for Server SPN, Use NTLM, and Use Trusted Connection
The driver now accepts variant spellings of the key names for these properties. When configuring these properties in a connection string or in the odbc.ini configuration file, you can use any of the listed key names:
- For the Server SPN property: Server_SPN or ServerSPN.
- For the Use NTLM and Use Trusted Connection properties: Integrated Security, Integrated_Security, or Trusted_Connection.
[MSSQL-698] Support for notarization
The driver now supports notarization on macOS systems, allowing it to be run on macOS versions 10.14.6 and later.
Resolved Issues The following issues have been resolved in Simba SQL Server ODBC Driver 1.5.1.
[MSSQL-366] When you run an INSERT, UPDATE, or DELETE query as a prepared statement, the driver incorrectly returns a row count of -1.
[MSSQL-692] In some cases, when driver logging is enabled at logging level 6 (TRACE), the driver returns incomplete log files and terminates unexpectedly.
[MSSQL-705] In some cases, when you run a query that contains a comment in the first line of the statement, the application that the driver is working in stops responding.
1.5.0 ————————————————————————
Released 2019-09-13
Enhancements & New Features
[MSSQL-656] Updated SQL Server version support
The driver now supports SQL Server versions 2012 to 2014.
[MSSQL-664] Updated driver version information in Linux binary
You can now check the Linux driver’s version from the driver binary file. To do this, open the .so file in a text editor, and search for the text “\(driver_version_sb\):”. The driver’s version number is listed after this text.
[MSSQL-627] Internal driver improvements
The driver has been updated with minor internal improvements.
[MSSQL-673] Updated third-party library linking for Linux
In the Linux driver, minor internal improvements have been implemented for the linking between the third-party libraries and the main driver library.
==============================================================================