[CT-394] [BUG] Console Log doesn't show model for Database Error

[spuders]

Is there an existing issue for this?

• I have searched the existing issues

Current Behaviour

When dbt run results in an database error at the end of the log information in console there is no information regarding the failing model. You have to scroll through the complete logging information to see which model fails.

20:14:54  
20:14:54  Finished running 1 view model in 0.33s.
20:14:54  
20:14:54  Completed with 1 error and 0 warnings:
20:14:54  
20:14:54  ('42000', '[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Falsche Syntax in der Nähe des as-Schlüsselworts. (156) (SQLMoreResults)')
20:14:54  
20:14:54  Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1

Expected Behaviour

As it was in previous versions. With concrete information like Database Error in model stg_orders (models/staging/stg_orders.sql)

20:14:54  
20:14:54  Finished running 1 view model in 0.33s.
20:14:54  
20:14:54  Completed with 1 error and 0 warnings:
20:14:54  Database Error in model error (models/playground/error.sql)
20:14:54  ('42000', '[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Falsche Syntax in der Nähe des as-Schlüsselworts. (156) (SQLMoreResults)')
20:14:54  
20:14:54  Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1

Steps to reproduce

Run simple model with an SQL Error

SELECT AS ERROR

This should result in an database error and an information which model failed.

What database are you using dbt with?

SQL Server

Additional context

I upgraded from dbt version 0.19.2 to 1.0.3. Since that I have this behaviour

[iknox-fa]

Hi @spuders thanks for the bug report! I'll look into it this afternoon.

[stu-k]

@spuders Thanks again for submitting the issue! Apologies for the long response time.
I wasn't able to determine whether this issue is coming from this repository, or the the SQLServer adapter repo, so we'll have to do a little more digging on this one.

There is a known issue in the SQL Server Adapter codebase that may be the cause of this issue. Though if the issue lies within dbt-core, it likely has to do with the way errors are being printed.

If any other community members or dbt-sqlserver adapter users have experienced this or similar issues, we would appreciate your input!

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.