# Table materialization

**URL:** <https://discourse.getdbt.com/t/table-materialization/20560>\
**Category:** Help\
**Tags:** databricks, dbt-core\
**Created:** [January 23, 2026, 11:51pm UTC](https://discourse.getdbt.com/t/table-materialization/20560 "2026-01-23T23:51:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![constantin-op](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@constantin-op](https://discourse.getdbt.com/u/constantin-op)\
**Post date:** [January 23, 2026, 11:51pm UTC](https://discourse.getdbt.com/t/table-materialization/20560/1 "2026-01-23T23:51:47Z")

</div>

## The problem I’m having

dbt model sql file + yml, the properties file stores column metatada and for esch column comment a new version is created.

## The context of why I’m trying to do this

Materialization table, dbt run model with 300 columns scheduled 4 times/day. Each run creates 300 versions in history.

## What I’ve already tried

I’ve tried to override persist\_docs (which is set on true at peoject level and I cannot change that) and now I’m thinking about writing a macro that would alter all columns in just one operation but I’m not sure if it is a good approach.

```auto

```