Release Notes > Connector and connectivity issues > SQL Server Connector
  

SQL Server Connector

Fixed issues

The tables in this section describe recent fixed issues for SQL Server connector in Metadata Command Center. Not all monthly releases include fixed issues.
October 2026 fixed issues
Issue
Description
SCAN-38673
When you run a job to extract metadata of stored procedures or functions that contain the DATEPART function with date or timestamp inputs, data lineage is not generated and the following error appears in the job log: Text 'YYYY-MM-DD' could not be parsed.
August 2024 fixed issues
Issue
Description
CDGC-64572
Data profiling tasks on Microsoft SQL Server catalog sources fail if the source data contains table or column names with Japanese multibyte characters.
SCAN-8203
When you run a Microsoft SQL Server catalog source job and extract a stored procedure that contains fullwidth digits, the metadata extraction job fails with the following error: Parse error (NoViableAlt) on token [...].
SCAN-8085
When you run a Microsoft SQL Server catalog source job, no columns get extracted from a table if the table contains a column without a name.
May 2024 fixed issues
Issue
Description
CDGC-60068
Data profiling tasks on Microsoft SQL Server catalog sources fail with the following error: Invalid Object or Invalid Column
This issue occurs if a column name includes a forward slash (/).
April 2024 fixed issues
Issue
Description
CDGC-60134
If you use Azure Active Directory authentication type when you create a connection to Microsoft Azure SQL catalog source, the profile tasks fail with the following error: Database Error: Failed to connect to database.
CDGC-60550
When you run data profiling tasks on a Microsoft SQL Server catalog source with a named instance, the first table is profiled successfully and profiling fails for the rest of the tables.