Skip to content

Update SQL server relations to not require an alias#604

Open
Benjamin-Knight wants to merge 4 commits into
dbt-msft:masterfrom
Benjamin-Knight:disable_alias
Open

Update SQL server relations to not require an alias#604
Benjamin-Knight wants to merge 4 commits into
dbt-msft:masterfrom
Benjamin-Knight:disable_alias

Conversation

@Benjamin-Knight
Copy link
Copy Markdown
Collaborator

Closes #595

Any project that uses the empty flag and expect the adapter to set aliases would find it no longer works.

Benjamin-Knight and others added 4 commits March 27, 2025 08:47
set dbt_sqlserver_disable_empty_relation_aliases default to True
keep SQL Server relation _render_limited_alias() hook for no-alias behavior
update empty-mode fixture SQL to use explicit user aliases so default no-alias behavior is valid
preserve opt-in flag path/test for user validation
@axellpadilla
Copy link
Copy Markdown
Collaborator

axellpadilla commented May 23, 2026

@Benjamin-Knight Please merge if ready, they reverted to true this for some reason for v1.10 microsoft/dbt-fabric@4aca77d
I added a workaround but that works only for empty and samples, and not for microbatching, this should be enough to avoid moving that important detail, microbatch can still be used on pure WITH statements

@Benjamin-Knight
Copy link
Copy Markdown
Collaborator Author

I'll double check this statement they have in the pull request for 1.10.

Updated the require_alias attribute in FabricRelation to True, aligning with dbt-core 1.10.0 requirements.

I do not remember seeing that requirement but will ensure that is the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--Empty flag only useful in the simplest projects

2 participants