From e843de7f3039c0cf51bc0fe59732d54264057968 Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Thu, 24 Oct 2024 11:14:38 +0100
Subject: [PATCH] Update
 website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md

---
 .../docs/cloud/connect-data-platform/connnect-bigquery.md     | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md b/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
index f83b9d0ef1d..904d4171b32 100644
--- a/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
+++ b/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
@@ -91,7 +91,11 @@ The `location` of BigQuery datasets can be set using the `location` setting in a
 
 When a `maximum_bytes_billed` value is configured for a BigQuery profile, that allows you to limit how much data your query can process. It’s a safeguard to prevent your query from accidentally processing more data than you expect, which could lead to higher costs. Queries executed by dbt will fail if they exceed the configured maximum bytes threshhold. This configuration should be supplied as an integer number of bytes.
 
+If your `maximum_bytes_billed` is 1000000000, you would enter that value in the `maximum_bytes_billed` field in dbt cloud.
 
+|  config | info | type | example |
+| ------- | ----| ----- | -------- |
+| max bytes billed | info here | integer | 100000 |