From f1e270b755c1f4f4bc31895962056b5cd1b12424 Mon Sep 17 00:00:00 2001
From: Dan Roscigno <dan@roscigno.com>
Date: Mon, 27 Feb 2023 15:41:52 -0500
Subject: [PATCH] Add link to Howto from Materialized view ref.

closes https://github.com/ClickHouse/clickhouse-docs/issues/96
---
 docs/en/sql-reference/statements/create/view.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/en/sql-reference/statements/create/view.md b/docs/en/sql-reference/statements/create/view.md
index 527b31b36a4..acdede3c673 100644
--- a/docs/en/sql-reference/statements/create/view.md
+++ b/docs/en/sql-reference/statements/create/view.md
@@ -54,6 +54,10 @@ SELECT * FROM view(column1=value1, column2=value2 ...)
 CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db.]table_name [ON CLUSTER] [TO[db.]name] [ENGINE = engine] [POPULATE] AS SELECT ...
 ```
 
+:::tip
+Here is a step by step guide on using [Materialized views](docs/en/guides/developer/cascading-materialized-views.md).
+:::
+
 Materialized views store data transformed by the corresponding [SELECT](../../../sql-reference/statements/select/index.md) query.
 
 When creating a materialized view without `TO [db].[table]`, you must specify `ENGINE` – the table engine for storing data.