Release Notes > Connector and connectivity issues > Microsoft SQL Server Connector
  

Microsoft SQL Server Connector

Fixed issues

The tables in this section describe recent fixed issues for Microsoft SQL Server connector in Metadata Command Center. Not all monthly releases include fixed issues.
October 2026 fixed issues
Issue
Description
CDGC-98325
When you run a data profiling job, the job fails with the following error: The number of elements in the select list exceeds the maximum allowed number of 4096 elements.
This issue occurs when the number of columns in a table exceeds 4096.
CDGC-97772
When you choose Custom Query as the sampling type to run data profiling or data quality tasks, the Sampling Query field incorrectly allows you to enter multiple values.
SCAN-38145
When you run a Microsoft SQL Server catalog source job, the job can't extract a stored procedure that contains an em space (U+2003) or a non-breaking space (U+00A0) character. The job fails with the following error: Parse error (NoViableAlt) on token: ' '
CDGC-93760
When you run a data profiling job, the job fails with the following error: Workflow generation failed for object: <object> with error: Unknown Codepage
This issue occurs when the connection uses a code page other than UTF-8.
SCAN-38146
When you run a metadata extraction job on stored procedures that contain 'BACKUP' statements with valued options in a 'WITH' clause, the job fails and the following error appears in the job log: Parse error (InputMismatch) on token: '='
SCAN-38357
When you run a metadata extraction job on stored procedures that contain the 'OPTIMIZE FOR' clause with numeric values, the job fails and the following error appears in the job log: Parse error (InputMismatch) on token: 'IF'
April 2026 fixed issues
Issue
Description
SCAN-31208
When you run a Microsoft SQL Server catalog source job, the job fails with the following error: Parse error (InputMismatch) on token: ';'
This issue occurs if the message body is empty.
CDGC-88152
For the Microsoft SQL Server Integration Services catalog source, when you try to remove a connection between two reference catalog sources, the DELETE job fails with the following errors:
  • - Connection unassignment failed in bulk metadata delete job
  • - Metadata delete job failed with error: Connect timed out
July 2025 fixed issues
Issue
Description
SCAN-20787
When you run a Microsoft SQL Server catalog source job to extract metadata from objects that contain an UNPIVOT clause and an IN clause in which the pivoted columns are qualified, the job succeeds, but the lineage is incomplete.