SQL Server OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
April 17, 2024¶
SQL OCF Connector: Version 1.5.0¶
Enhancements¶
With Alation version 2024.1 and SQL Server OCF connector version 1.5.0, Alation has introduced an enhanced user interface for configuring the SQL Server data source settings.
Note
The connector version is compatible with Alation versions prior to 2023.3.4. However, you will view the old user interface with Alation versions prior to 2024.1.
The documentation for the new SQL Server experience is available at : SQL Server OCF Connector.
The enhanced user interface provides the following features:
Better User Experience¶
The enhanced SQL Server user interface provides better navigation and multiple visual cues, making it easy to configure and manage SQL Server data source.
Easy to Connect¶
The SQL Server user interface now provides a step-by-step process to connect to your SQL Server data source easily and quickly.
Additional Error-Prevention Checks¶
The SQL Server user interface now includes added checks to avoid obvious configuration mistakes. The user interface also includes text to assist and provide cues while configuring.
Detailed Error Reports and Troubleshooting Support¶
The improved SQL Server user interface makes troubleshooting easier for metadata extraction and query log ingestion, as you can now have a detailed error report for both processes. The report contains a detailed error description and steps to resolve the issue. (AL-139399).
February 28, 2024¶
SQL OCF Connector: Version 1.4.0¶
Enhancements¶
Docker CIS Benchmark Compliance¶
SQL OCF connector versions 2.3.0 and newer are now compliant with the following Docker CIS benchmarks:
Docker 4.1 - Ensures that a user for the container is created
Docker 4.6 - Ensures that HEALTHCHECK instructions are added to container images
Docker 4.7 - Ensures that docker files do not include update instructions as a standalone or single-line instruction
January 10, 2024¶
SQL Server OCF Connector: Version 1.3.10¶
Fixed Issues¶
VIEW Columns Fail to Display the Column Length¶
VIEW columns in SQL OCF connector do not display the column length or limit along with the data type name.
January 03, 2024¶
SQL Server OCF Connector: Version 1.3.9¶
Fixed Issues¶
QLI Jobs Display Incorrect Job Status for Errors¶
A QLI is completed with Partial Success status even when there are errors and the error message is displayed only in the connector logs.
December 20, 2023¶
SQL Server OCF Connector: Version 1.3.8¶
Fixed Issues¶
SQL Server Connection Error Soft Deletes Cataloged Objects¶
In SQL Server OCF Connector, an error in the SQL server connection caused an empty stream of data, which was treated as a successful MDE and resulted in the soft deletion of all the extracted metadata.
Alation now ensures that such configuration and connection errors result in metadata extraction failure instead of an empty data stream.
November 8, 2023¶
SQL Server OCF Connector Version 1.3.7¶
Compatible Alation version: 2022.2 or higher
Fixed Issues¶
Connection Test Fails When Using SSL with NTLM Authentication¶
Fixed an issue when the connection test failed when SSL was enabled with NTLM authentication. The test resulted in the following error:
Caused by: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
To use SSL with NTLM, basic, or Kerberos authentication, use the following JDBC URL format:
sqlserver://<Host_Name>:<Port_Number>;encrypt=true;hostNameInCertificate=<certificate_name>;
This JDBC URI includes the following additional SSL related parameters:
encrypt=true
hostNameInCertificate=<certificate_name>
You can run the command below to verify your certificate name. In the result, check for the value after CN=. That’s the certificate name.
openssl x509 -noout -subject -in <certificate_name>.crt;
Example:
sqlserver://10.13.82.165:1433;encrypt=true;hostNameInCertificate=abc.corp.net;