Skip to main content
A data asset can be certified, which means it is the one to use, or deprecated, which means people should stop using it. Each mark shows who set it, when and why. People see the marks on the asset page. AI assistants that use the Coalesce Quality MCP server see them too, so an assistant can pick the certified table and tell you when a table it looks at is deprecated. You can mark any data asset, for example a table, a view, a dbt model or a semantic model. A mark set on a dbt model also applies to the table that the model builds.

Certify or deprecate an asset

  1. Open the asset page.
  2. Click Marks in the header and select Certify or Deprecate.
  3. Optionally, enter a reason. When you deprecate, name the asset to use instead, for example use analytics.orders_v2 instead.
  4. Click Certify or Deprecate to confirm.
A badge appears next to the asset name. Hover over it to see who set the mark, when, and the reason. To remove a mark, click Marks and select Remove certification or Remove deprecation. To see every change to the marks of the asset, select See history. The history also shows the marks set on a linked asset, like the dbt model that builds a table.

Who can set a mark

Read more about owners and user roles.

See all certified and deprecated assets

Go to . Next to the context entries, the page has three tabs for the marks.
  • Certified and deprecated lists the certified or the deprecated assets. The Certified / Deprecated switch picks the mark, and By me shows only the marks you set. The catalog filters narrow the list. An asset that the deprecation query selects shows Deprecation query in the By column.
  • Mark history lists every change to a mark in the workspace, newest first, with who made it, when and why. Changes to the deprecation query are listed too.
  • Deprecation query holds the query that deprecates assets in bulk, described below.

Deprecate assets with a query

A workspace can have one deprecation query. Every asset that matches the query is deprecated, including assets that appear after you save it. Use it to deprecate a whole legacy schema, or every table that carries a label in your warehouse.
  1. Go to .
  2. Select the assets with the filters: Browser, Name search, Type, Platform, Annotation, Product or a ResolverQL query. The page shows the number of matching assets and the list of them, so you can check the selection before you save it.
  3. Optionally, enter a reason. The reason shows on every asset that matches.
  4. Click Save changes.
The badge of a matching asset says Deprecated by the workspace query, with a link to the query. You cannot remove this deprecation from the asset page, only by changing the query. You cannot save a query that uses with_mark(...), also when it reaches with_mark(...) through an owner or a data product that it selects.

Deprecate by a warehouse label

If your team already tags legacy tables in the warehouse, you can deprecate them by that tag. Table tags and labels arrive in Coalesce Quality as annotations, and the deprecation query can select by annotation. For example, a Snowflake tag DWH_TESTING.GOVERNANCE.LIFECYCLE set to 'legacy' on a table becomes the annotation snowflake.dwh_testing.governance.lifecycle with the value legacy.
  1. Open the deprecation query.
  2. Add an Annotation filter on snowflake.dwh_testing.governance.lifecycle with the value legacy.
  3. Enter a reason, for example Tagged as legacy in Snowflake, and click Save changes.
Every table with this tag is now deprecated. When someone tags another table later, it is deprecated after the next catalog refresh, with no step in Coalesce Quality. Only a tag set on the table itself becomes an annotation. A tag inherited from a database or a schema does not.

Filter the Catalog by mark

On the page, click Add filter, select Mark, then Certified, Deprecated or both. Change is to is not to hide the marked assets, for example to list every revenue table that is not deprecated. The filter also matches the assets certified or deprecated in Coalesce Catalog. In a ResolverQL query, the same filter is with_mark(kind="certified") or with_mark(kind="deprecated").

Stop monitoring deprecated assets

A deprecated table usually does not need monitors. To keep the deprecated assets out of all deployment rules, add an exclusion rule with this ResolverQL query:
The rule also covers the assets that the deprecation query selects, so a table that gets the legacy tag in the warehouse loses its automatic monitors too.

Certified semantic models

Several semantic models can define a metric with the same name. On the page of such a metric, Coalesce Quality names the definition to use only if all of these are true:
  • Exactly one of the models is certified.
  • The definition of that model did not change after it was certified.
  • That model is not deprecated.
If no model or more than one model is certified, Coalesce Quality does not pick one, and you should ask the owners of the models. A certification covers the definition of the model: its expressions, filters, relationships and keys. If the definition changes after the certification, the badge shows Certification outdated, and the model no longer counts as certified. A change to a description or a display name does not count. To confirm that the new definition is still the one to use, click Marks and select Certify again.

AI assistants and the API

The Coalesce Quality MCP server has tools to read, list, set and remove marks. get_metric_definitions uses the marks to name the definition of a metric to use. No MCP tool changes the deprecation query. In the API, synq.entities.marks.v1alpha.EntityMarksService reads and sets the marks and the deprecation query. Setting marks needs SCOPE_ENTITY_MARKS_EDIT, or SCOPE_ENTITY_MARKS_OWNED_EDIT for the assets you own. See the API reference and API scopes. This API is in alpha, and its shape can change.