[BUG] When database (MS SQLServer) has case sensitive collation SQL_Latin1_General_CP1_CS_AS the Latest_open cte table is not found because incorrect capital letter

[koillinengit]

Describe the bug
When database (sqlserver) has case sensitive collation SQL_Latin1_General_CP1_CS_AS the Latest_open cte table is not found because incorrect capital letter

Environment

dbt version: 1.2.4
dbtvault version: 0.9.3
Database/Platform: Sqlserver

To Reproduce
Steps to reproduce the behavior:

1. dbt run
2. See error: ('42S02', "[42S02] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid object name 'Latest_open'. (208) (SQLExecDirectW)")

Expected behavior
Dbt run command for effectivity satellites should go without errors even if database has case sensitive collation: SQL_Latin1_General_CP1_CS_AS instead of case insensitive SQL_Latin1_General_CP1_CI_AS

Screenshots

Log files
('42S02', "[42S02] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid object name 'Latest_open'. (208) (SQLExecDirectW)")

Additional context
Add any other context about the problem here.

[DVAlexHiggs]

dbtvault does not currently support Azure Synapse, only the following are supported:

• Snowflake
• Bigquery
• Postgres
• Databricks
• MS SQLServer

Please our documentation for more details.

Because we do not yet support Synapse, you will get unpredictable behavior such as this.

Until we add Azure Synapse support, you may extend dbtvault and add in Azure Synapse specific code yourself.

Please see the dbt docs for more info on this as well.

This is quite a simple fix from our side and if it's already working other than this, then we can add this in the next update. The capital 'L' is not intended so it should be changed. Thanks for this report.

[koillinengit]

The same issue is in MS SQLServer

[koillinengit]

In the snowflake version this seems to be fixed (which is case sensitive by default), but not in thisSQLserver version...

[DVAlexHiggs]

In the snowflake version this seems to be fixed (which is case sensitive by default), but not in thisSQLserver version...

Thank you. We'll get this fixed in the next release. Must have slipped through QC!

[DVAlexHiggs]

Hi! Fixed in 0.9.5. Thanks for your patience.