Generating changelog fails for MSSQL 2019 when sys.synonyms exist

[catholic-indulgence-vaper]

Environment

Liquibase Version: 4.4.3

Liquibase Integration & Version: CLI

Liquibase Extension(s) & Version:

Database Vendor & Version: MSSQL 2019

Operating System Type & Version: Linux

Description

Generating changelog fails.

Steps To Reproduce

List the steps to reproduce the behavior.

• ./liquibase generateChangeLog

Actual Behavior

Error thrown:
Unexpected error running Liquibase: Error executing SQL SELECT NULL AS SYNONYM_CATALOG_NAME, SCHEMA_NAME(SCHEMA_ID) as SYNONYM_SCHEMA_NAME, name as SYNONYM_NAME, NULL AS OBJECT_CATALOG_NAME, NULL AS OBJECT_SCHEMA_NAME, PARSENAME(BASE_OBJECT_NAME,1) AS OBJECT_NAME, PARSENAME(BASE_OBJECT_NAME,2) AS OBJECT_SCHEMA_NAME, PARSENAME(BASE_OBJECT_NAME,3) AS OBJECT_CATALOG_NAME FROM SYS.SYNONYMS WHERE SCHEMA_NAME(SCHEMA_ID)='dbo' AND name='some_table_name' AND IS_MS_SHIPPED='false': Invalid object name 'SYS.SYNONYMS'.

MSSQL 2019 fails when sys.synonyms is in upper case.

Expected/Desired Behavior

Changelog is generated.

MSSQL 2019 expects sys.synonyms to be in lower case.

[molivasdat]

Hi @catholic-indulgence-vaper Thanks for creating this issue. Is the server running on Linux or are you running the from Linux. Is this a default configuration of MS SQL 2019? Just trying to get a sense to recreate this.

[catholic-indulgence-vaper]

Hello, @molivasdat!
This is default MSSQL server running in Docker image with default parameters.

Just found out that dabases with collation Cyrillic_General_CI_AS do accept this query.
Databases with collation Cyrillic_General_BIN no not!

Example from Azure studio, database with Cyrillic_General_BIN:
PMStarted executing query at Line 1 Msg 208, Level 16, State 1, Line 1 Invalid object name 'SYS.SYNONYMS'. Total execution time: 00:00:00.001