Merge branch 'ClickHouse:main' into update_clusters_tutorial

Author: Blargian

.gitignore

@@ -68,3 +68,4 @@ docs/cloud/reference/release-notes-index.md
 docs/whats-new/changelog/index.md
 docs/cloud/manage/api/api-reference-index.md
 docs/getting-started/index.md
+docs/data-modeling/projections/index.md

docs/about-us/cloud.md

@@ -11,7 +11,7 @@ title: 'ClickHouse Cloud'
 ClickHouse Cloud is the cloud offering created by the original creators of the popular open-source OLAP database ClickHouse. 
 You can experience ClickHouse Cloud by [starting a free trial](https://console.clickhouse.cloud/signUp).
 
-### ClickHouse Cloud benefits: {#clickhouse-cloud-benefits}
+## ClickHouse Cloud benefits {#clickhouse-cloud-benefits}
 
 Some of the benefits of using ClickHouse Cloud are described below:
 
@@ -22,7 +22,28 @@ Some of the benefits of using ClickHouse Cloud are described below:
 - **Total cost of ownership**: Best price / performance ratio and low administrative overhead.
 - **Broad ecosystem**: Bring your favorite data connectors, visualization tools, SQL and language clients with you.
 
-### What version of ClickHouse does ClickHouse Cloud use? {#what-version-of-clickhouse-does-clickhouse-cloud-use}
+<!--
+## OSS vs ClickHouse Cloud comparison {#oss-vs-clickhouse-cloud}
+
+| Feature                        | Benefits                                                                                                                                                                                                                                                                                                   | OSS ClickHouse  | ClickHouse Cloud  |
+|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------|
+| **Deployment modes**           | ClickHouse provides flexibility to self-manage with open-source or deploy in the cloud. Use ClickHouse Local for local files without a server or chDB to embed ClickHouse directly into your application.                                                                                                  | ✅               | ✅                 |
+| **Storage**                    | As an open-source and cloud-hosted product, ClickHouse can be deployed in both shared-disk and shared-nothing architectures.                                                                                                                                                                               | ✅               | ✅                 |
+| **Monitoring and alerting**    | Monitoring and alerting about the status of your services is critical to ensuring optimal performance and a proactive approach to detect and triage potential issues.                                                                                                                                      | ✅               | ✅                 |
+| **ClickPipes**                 | ClickPipes is ClickHouse's managed ingestion pipeline that allows you to seamlessly connect your external data sources like databases, APIs, and streaming services into ClickHouse Cloud, eliminating the need for managing pipelines, custom jobs, or ETL processes. It supports workloads of all sizes. | ❌               | ✅                 |
+| **Pre-built integrations**     | ClickHouse provides pre-built integrations that connect ClickHouse to popular tools and services such as data lakes, SQL and language clients, visualization libraries, and more.                                                                                                                          | ❌               | ✅                 |
+| **SQL console**                | The SQL console offers a fast, intuitive way to connect, explore, and query ClickHouse databases, featuring a slick caption, query interface, data import tools, visualizations, collaboration features, and GenAI-powered SQL assistance.                                                                 | ❌               | ✅                 |
+| **Compliance**                 | ClickHouse Cloud compliance includes CCPA, EU-US DPF, GDPR, HIPAA, ISO 27001, ISO 27001 SoA, PCI DSS, SOC2. ClickHouse Cloud's security, availability, processing integrity, and confidentiality processes are all independently audited. Details: trust.clickhouse.com.                                   | ❌               | ✅                 |
+| **Enterprise-grade security**  | Support for advanced security features such as SSO, multi-factor authentication, role-based access control (RBAC), private and secure connections with support for Private Link and Private Service Connect, IP filtering, customer-managed encryption keys (CMEK), and more.                              | ❌               | ✅                 |
+| **Scaling and optimization**   | Seamlessly scales up or down based on workload, supporting both horizontal and vertical scaling. With automated backups, replication, and high availability, ClickHouse, it provides users with optimal resource allocation.                                                                               | ❌               | ✅                 |
+| **Support services**           | Our best-in-class support services and open-source community resources provide coverage for whichever deployment model you choose.                                                                                                                                                                         | ❌               | ✅                 |
+| **Database upgrades**          | Regular database upgrades are essential to establish a strong security posture and access the latest features and performance improvements.                                                                                                                                                                | ❌               | ✅                 |
+| **Backups**                    | Backups and restore functionality ensures data durability and supports graceful recovery in the event of outages or other disruptions.                                                                                                                                                                     | ❌               | ✅                 |
+| **Compute-compute separation** | Users can scale compute resources independently of storage, so teams and workloads can share the same storage and maintain dedicated compute resources. This ensures that the performance of one workload doesn't interfere with another, enhancing flexibility, performance, and cost-efficiency.         | ❌               | ✅                 |
+| **Managed services**           | With a cloud-managed service, teams can focus on business outcomes and accelerate time-to-market without having to worry about the operational overhead of sizing, setup, and maintenance of ClickHouse.                                                                                                   | ❌               | ✅                 |
+-->
+
+## What version of ClickHouse does ClickHouse Cloud use? {#what-version-of-clickhouse-does-clickhouse-cloud-use}
 
 Clickhouse Cloud continuously upgrades your service to a newer version. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.
 

docs/best-practices/using_data_skipping_indices.md

@@ -140,7 +140,7 @@ LIMIT 1
 A simple analysis shows that `ViewCount` is correlated with the `CreationDate` (a primary key) as one might expect - the longer a post exists, the more time it has to be viewed.
 
 ```sql
-SELECT toDate(CreationDate) as day, avg(ViewCount) as view_count FROM stackoverflow.posts WHERE day > '2009-01-01'  GROUP BY day
+SELECT toDate(CreationDate) AS day, avg(ViewCount) AS view_count FROM stackoverflow.posts WHERE day > '2009-01-01'  GROUP BY day
 ```
 
 This therefore makes a logical choice for a data skipping index. Given the numeric type, a min_max index makes sense. We add an index using the following `ALTER TABLE` commands - first adding it, then "materializing it".

docs/cloud/get-started/index.md

@@ -9,8 +9,7 @@ Welcome to ClickHouse Cloud! Explore the pages below to learn more about what Cl
 
 | Page                     | Description                                                                                                                                               |
 |--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Overview](/cloud/overview)          | Overview of the benefits of using ClickHouse Cloud and what version of ClickHouse is used for it.                                                         | 
-| [Cloud Quick Start](/cloud/get-started/cloud-quick-start) | Quick start guide to get up and running with Cloud.                                                                                                       |
+| [Overview](/cloud/overview)          | Overview of the benefits of using ClickHouse Cloud and what version of ClickHouse is used for it.                                                         |
 | [SQL Console](/cloud/get-started/sql-console)       | Learn about the interactive SQL console available in Cloud                                                                                                |
 | [Query Insights](/cloud/get-started/query-insights)    | Learn about how Cloud's Query Insights feature makes ClickHouse's built-in query log easier to use through various visualizations and tables.             |
 | [Query Endpoints](/cloud/get-started/query-endpoints)   | Learn about the Query API Endpoints feature which allows you to create an API endpoint directly from any saved SQL query in the ClickHouse Cloud console. |

docs/cloud/get-started/query-endpoints.md

@@ -29,16 +29,16 @@ If you have a saved query, you can skip this step.
 Open a new query tab. For demonstration purposes, we'll use the [youtube dataset](/getting-started/example-datasets/youtube-dislikes), which contains approximately 4.5 billion records. As an example query, we'll return the top 10 uploaders by average views per video in a user-inputted `year` parameter:
 
 ```sql
-with sum(view_count) as view_sum,
-    round(view_sum / num_uploads, 2) as per_upload
-select
+WITH sum(view_count) AS view_sum,
+    round(view_sum / num_uploads, 2) AS per_upload
+SELECT
     uploader,
-    count() as num_uploads,
-    formatReadableQuantity(view_sum) as total_views,
-    formatReadableQuantity(per_upload) as views_per_video
-from
+    count() AS num_uploads,
+    formatReadableQuantity(view_sum) AS total_views,
+    formatReadableQuantity(per_upload) AS views_per_video
+FROM
     youtube
-where
+WHERE
     toYear(upload_date) = {year: UInt16}
 group by uploader
 order by per_upload desc
@@ -149,7 +149,7 @@ To upgrade the endpoint version from `v1` to `v2`, include the `x-clickhouse-end
 **Query API Endpoint SQL:**
 
 ```sql
-SELECT database, name as num_tables FROM system.tables limit 3;
+SELECT database, name AS num_tables FROM system.tables LIMIT 3;
 ```
 
 #### Version 1 {#version-1}
@@ -365,7 +365,7 @@ OK
 **Query API Endpoint SQL:**
 
 ```sql
-SELECT * from system.tables;
+SELECT * FROM system.tables;
 ```
 
 **cURL:**
@@ -401,7 +401,7 @@ fetch(
 **Query API Endpoint SQL:**
 
 ```sql
-SELECT name, database from system.tables;
+SELECT name, database FROM system.tables;
 ```
 
 **Typescript:**

docs/cloud/get-started/sql-console.md

@@ -251,17 +251,17 @@ Query result sets can be easily exported to CSV format directly from the SQL con
 Some data can be more easily interpreted in chart form. You can quickly create visualizations from query result data directly from the SQL console in just a few clicks. As an example, we'll use a query that calculates weekly statistics for NYC taxi trips:
 
 ```sql
-select
-   toStartOfWeek(pickup_datetime) as week,
-   sum(total_amount) as fare_total,
-   sum(trip_distance) as distance_total,
-   count(*) as trip_total
-from
+SELECT
+   toStartOfWeek(pickup_datetime) AS week,
+   sum(total_amount) AS fare_total,
+   sum(trip_distance) AS distance_total,
+   count(*) AS trip_total
+FROM
    nyc_taxi
-group by
+GROUP BY
    1
-order by
-   1 asc
+ORDER BY
+   1 ASC
 ```
 
 <Image img={tabular_query_results} size="md" alt='Tabular query results' />

docs/cloud/manage/upgrades.md

@@ -39,7 +39,16 @@ You will not be charged for the time that the service is under maintenance. _Mai
 
 ## Release channels (upgrade schedule) {#release-channels-upgrade-schedule}
 
-You are able to specify the upgrade schedule for your ClickHouse Cloud service by subscribing to a specific release channel.
+Users are able to specify the upgrade schedule for their ClickHouse Cloud service by subscribing to a specific release channel. There are three release channels, and the user has the ability to configure the day and time of the week for upgrades with the **scheduled upgrades** feature.
+
+The three release channels are:
+- The [**fast release channel**](#fast-release-channel-early-upgrades) for early access to upgrades.
+- The [**regular release channel**](#regular-release-channel) is the default, and upgrades on this channel start two weeks after the fast release channel upgrades. If your service on the Scale and Enterprise tier does not have a release channel set, it is on the regular release channel by default.
+- The [**slow release channel**](#slow-release-channel-deferred-upgrades) is for deferred release. Upgrades on this channel occur two weeks after the regular release channel upgrades.
+
+:::note
+Basic tier services are automatically enlisted to the fast release channel
+:::
 
 ### Fast release channel (early upgrades) {#fast-release-channel-early-upgrades}
 
@@ -76,6 +85,18 @@ Upgrades to the regular release channel are typically performed two weeks after
 Basic tier services are upgraded soon after the Fast release channel.
 :::
 
+### Slow release channel (deferred upgrades) {#slow-release-channel-deferred-upgrades}
+
+<EnterprisePlanFeatureBadge feature="The slow release channel"/>
+
+We offer a **Slow release** channel if you would like your services to receive upgrades after the regular release schedule.
+
+Specifically, services will:
+
+- Be upgraded after the Fast and Regular release channels roll-outs are complete
+- Receive ClickHouse releases ~ 2 weeks after the regular release
+- Be meant for customers that want additional time to test ClickHouse releases on their non-production environments before the production upgrade. Non-production environments can either get upgrades on the Fast or the Regular release channel for testing and validation.
+
 ## Scheduled upgrades {#scheduled-upgrades}
 
 <EnterprisePlanFeatureBadge feature="Scheduled upgrades" linking_verb_are="true"/>

docs/cloud/reference/changelog.md

@@ -30,10 +30,21 @@ import query_endpoints from '@site/static/images/cloud/reference/may-17-query-en
 import dashboards from '@site/static/images/cloud/reference/may-30-dashboards.png';
 
 In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/cloud/reference/cloud-compatibility.md) page.
-## June 13, 2025 {#june-13-2025}
 
-- We're excited to announce that ClickHouse Cloud Dashboards are now generally available. Dashboards allow users to visualize queries on dashboards, interact with data via filters and query parameters, and manage sharing. 
+## June 27, 2025 {#june-27-2025}
+
+- We now officially support a Terraform provider for managing database privileges
+  which is also compatible with self-managed deployments. Please refer to the
+  [blog](https://clickhouse.com/blog/new-terraform-provider-manage-clickhouse-database-users-roles-and-privileges-with-code)
+  and our [docs](https://registry.terraform.io/providers/ClickHouse/clickhousedbops/latest/docs)
+  for more information.
+- Enterprise tier services can now enlist in the [slow release channel](/manage/updates/#slow-release-channel-deferred-upgrades) to defer 
+  upgrades by two weeks after the regular release to permit additional time for 
+  testing.
+
+## June 13, 2025 {#june-13-2025}
 
+- We're excited to announce that ClickHouse Cloud Dashboards are now generally available. Dashboards allow users to visualize queries on dashboards, interact with data via filters and query parameters, and manage sharing.
 - API key IP filters: we are introducing an additional layer of protection for your interactions with ClickHouse Cloud. When generating an API key, you may setup an IP allow list to limit where the API key may be used.  Please refer to the [documentation](https://clickhouse.com/docs/cloud/security/setting-ip-filters) for details. 
 
 ## May 30, 2025 {#may-30-2025}

docs/cloud/reference/warehouses.md

@@ -135,8 +135,8 @@ Once compute-compute is enabled for a service (at least one secondary service wa
 6. **CREATE/RENAME/DROP DATABASE queries could be blocked by idled/stopped services by default.** These queries can hang. To bypass this, you  can run database management queries with `settings distributed_ddl_task_timeout=0` at the session or per query level. For example:
 
 ```sql
-create database db_test_ddl_single_query_setting
-settings distributed_ddl_task_timeout=0
+CREATE DATABASE db_test_ddl_single_query_setting
+SETTINGS distributed_ddl_task_timeout=0
 ```
 
 6. **In very rare cases, secondary services that are idled or stopped for a long time (days) without waking/starting up can cause performance degradation to other services in the same warehouse.** This issue will be resolved soon and is connected to mutations running in the background. If you think you are experiencing this issue, please contact ClickHouse [Support](https://clickhouse.com/support/program).

docs/data-modeling/backfilling.md

@@ -371,7 +371,7 @@ While we can add the target table, prior to adding the materialized view we modi
 ```sql
 CREATE MATERIALIZED VIEW pypi_downloads_per_day_mv TO pypi_downloads_per_day
 AS SELECT
- toStartOfHour(timestamp) as hour,
+ toStartOfHour(timestamp) AS hour,
  project, count() AS count
 FROM pypi WHERE timestamp >= '2024-12-17 09:00:00'
 GROUP BY hour, project