From ded4a495732cd3f361c090a10d2c8c9dfd7cae71 Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Fri, 6 Jun 2025 10:00:01 -0400
Subject: [PATCH 01/25] add db2 to supported retl sources

---
 src/connections/reverse-etl/setup.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md
index 0fdd98bd7c..88cf060cd7 100644
--- a/src/connections/reverse-etl/setup.md
+++ b/src/connections/reverse-etl/setup.md
@@ -28,6 +28,7 @@ To add your warehouse as a source:
   - [Azure Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup)
   - [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup)
   - [Databricks Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup)
+  - [DB2 Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup)
   - [Postgres Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup)
   - [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup)
   - [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup)

From 53a2fc0fec42e28a0c0cf4c1c04757987df04381 Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Fri, 6 Jun 2025 10:27:47 -0400
Subject: [PATCH 02/25] add db2 setup guide

---
 .../db2-setup.md                              | 70 +++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
new file mode 100644
index 0000000000..6a4d561d04
--- /dev/null
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -0,0 +1,70 @@
+---
+title: DB2 Reverse ETL Setup
+---
+
+Set up DB2 as your Reverse ETL source.
+
+At a high level, when you set up DB2 for Reverse ETL, the configured database user must have read permissions on any tables involved in the query, and write permissions on a managed schema (`SEGMENT_REVERSE_ETL`) that Segment uses to track sync progress. Authentication is handled through username and password credentials configured in the Segment app.
+
+
+
+## Required permissions
+
+In order to run a Reverse-ETL sync in a DB2 warehouse, Segment needs the following permissions:
+
+1. **Permission to read from all tables used in the model** (i.e., the tables included in your SELECT query).
+2. **Permission to create and manage a schema** for tracking sync metadata.
+
+
+> info "Use a dedicated user for Segment"
+> It's recommended to create a dedicated DB2 user for Segment with access limited to only the relevant schemas and tables.
+
+1. Open the Db2 warehouse and navigate to  **Administration > User management**.
+2. Click **Add**.
+3. Create a new user account with *user* privileges. Make sure you save the username and password, as these are required to set up the Segment configuration in a later step.
+
+
+> info ""
+> The `SEGMENT_REVERSE_ETL` schema will be created and managed by Segment to track the status of each sync. 
+> You can also choose to create this schema yourself by running: 
+> `CREATE SCHEMA SEGMENT_REVERSE_ETL` 
+> and explicitly grant Segment privileges on it.
+
+
+
+Run the below SQL commands to grant Segment the required permissions:
+
+```sql
+-- Grant permissions to create manage objects within the SEGMENT_REVERSE_ETL schema
+GRANT CREATEIN, DROPIN ON SCHEMA SEGMENT_REVERSE_ETL TO USER <username>;
+GRANT CREATETAB ON DATABASE TO USER <username>;
+
+-- Grant read access on each table used in the model
+GRANT SELECT ON TABLE <schema_name>.<table_name> TO USER <username>;
+```
+
+
+## Set up guide
+
+To set up DB2 as your Reverse ETL source:
+
+1. Make sure your DB2 database is network-accessible from [Segment's IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).
+2. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}.
+3. Navigate to **Connections > Sources** and select the **Reverse ETL** tab.
+4. Click **+ Add Reverse ETL source**.
+5. Select **DB2** and click **Add Source**.
+6. Enter the configuration settings for your DB2 source:
+  * Hostname: `<hostname>`
+  * Port: `<port>` (default)
+  * Database: `<db_name>`
+  * Username: `<segment_db2_user>`
+  * Password: `<password>`
+  * Schema [optional]: If not specified, Segment will use the user’s default schema
+7. Click **Test Connection** to validate the setup.
+8. If the connection is successful, click **Add source**.
+
+> warning ""
+> Segment only supports user/password authentication for DB2.
+> Ensure that your DB2 instance is configured to allow remote connections and the user has the necessary permissions.
+
+After you've successfully added your DB2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.

From 0fb8cb6842617a2c97b55cf46fab8293aa6f4b11 Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Fri, 6 Jun 2025 17:03:34 -0400
Subject: [PATCH 03/25] [netlify-build]


From efae4b289f7bde34ab9b48ae94c287f821667f03 Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Fri, 6 Jun 2025 22:28:55 -0400
Subject: [PATCH 04/25] [netlify-build] add DB2 source to dropdown menu

---
 src/_data/sidenav/main.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
index 8fcf0bfa3e..d73e7ddb26 100644
--- a/src/_data/sidenav/main.yml
+++ b/src/_data/sidenav/main.yml
@@ -210,6 +210,8 @@ sections:
         title: BigQuery Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup
         title: Databricks Reverse ETL Setup
+      - path: /connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup
+        title: DB2 Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup
         title: Postgres Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup

From cd96a3a51cd2df0f8ed021f6da252a73e5556413 Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Sun, 8 Jun 2025 12:12:15 -0400
Subject: [PATCH 05/25] [netlify-build] small fixes

---
 .../reverse-etl-source-setup-guides/db2-setup.md          | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 6a4d561d04..b7ef7cf8df 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -21,7 +21,7 @@ In order to run a Reverse-ETL sync in a DB2 warehouse, Segment needs the followi
 
 1. Open the Db2 warehouse and navigate to  **Administration > User management**.
 2. Click **Add**.
-3. Create a new user account with *user* privileges. Make sure you save the username and password, as these are required to set up the Segment configuration in a later step.
+3. Create a new user with *user* privileges. Make sure you save the username and password, as these are required to set up the Segment configuration in a later step.
 
 
 > info ""
@@ -55,7 +55,7 @@ To set up DB2 as your Reverse ETL source:
 5. Select **DB2** and click **Add Source**.
 6. Enter the configuration settings for your DB2 source:
   * Hostname: `<hostname>`
-  * Port: `<port>` (default)
+  * Port: `<port>`
   * Database: `<db_name>`
   * Username: `<segment_db2_user>`
   * Password: `<password>`
@@ -63,8 +63,4 @@ To set up DB2 as your Reverse ETL source:
 7. Click **Test Connection** to validate the setup.
 8. If the connection is successful, click **Add source**.
 
-> warning ""
-> Segment only supports user/password authentication for DB2.
-> Ensure that your DB2 instance is configured to allow remote connections and the user has the necessary permissions.
-
 After you've successfully added your DB2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.

From 9f68558f345706dae2c2971ecdd2c460bf783ffa Mon Sep 17 00:00:00 2001
From: Gil Omer <gil.omer@segment.com>
Date: Mon, 9 Jun 2025 10:04:21 -0400
Subject: [PATCH 06/25] [netlify-build] more fixes

---
 .../db2-setup.md                              | 30 +++++++++++--------
 1 file changed, 17 insertions(+), 13 deletions(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index b7ef7cf8df..f72827138d 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -10,57 +10,61 @@ At a high level, when you set up DB2 for Reverse ETL, the configured database us
 
 ## Required permissions
 
-In order to run a Reverse-ETL sync in a DB2 warehouse, Segment needs the following permissions:
+In order to run a Reverse ETL sync in a DB2 warehouse, Segment needs the following permissions:
 
-1. **Permission to read from all tables used in the model** (i.e., the tables included in your SELECT query).
-2. **Permission to create and manage a schema** for tracking sync metadata.
+* **Permission to read from all tables used in the model** (i.e., the tables included in your SELECT query).
+* **Permission to create and manage a schema** for tracking sync metadata.
+* **Permission to create tables in the database**, needed for internal metadata tables.
 
 
 > info "Use a dedicated user for Segment"
 > It's recommended to create a dedicated DB2 user for Segment with access limited to only the relevant schemas and tables.
 
-1. Open the Db2 warehouse and navigate to  **Administration > User management**.
+1. In IBM Cloud, go to your DB2 instance and navigate to **Administration > User management**.
 2. Click **Add**.
-3. Create a new user with *user* privileges. Make sure you save the username and password, as these are required to set up the Segment configuration in a later step.
+3. Create a new user with *user* privileges. Make sure to save the username and password—these are needed to configure the Segment
+   source connection later.
 
 
 > info ""
 > The `SEGMENT_REVERSE_ETL` schema will be created and managed by Segment to track the status of each sync. 
 > You can also choose to create this schema yourself by running: 
 > `CREATE SCHEMA SEGMENT_REVERSE_ETL` 
-> and explicitly grant Segment privileges on it.
+> Then grant Segment the appropriate privileges.
 
 
 
-Run the below SQL commands to grant Segment the required permissions:
+Run the following SQL commands to grant Segment the required permissions:
 
 ```sql
--- Grant permissions to create manage objects within the SEGMENT_REVERSE_ETL schema
+-- Grant permissions to create and manage objects within the SEGMENT_REVERSE_ETL schema
 GRANT CREATEIN, DROPIN ON SCHEMA SEGMENT_REVERSE_ETL TO USER <username>;
+
+-- Grant permission to create tables in the database
 GRANT CREATETAB ON DATABASE TO USER <username>;
 
 -- Grant read access on each table used in the model
 GRANT SELECT ON TABLE <schema_name>.<table_name> TO USER <username>;
+-- Repeat the above command for all tables involved in your model
 ```
 
 
-## Set up guide
+## Set Up Guide
 
 To set up DB2 as your Reverse ETL source:
 
 1. Make sure your DB2 database is network-accessible from [Segment's IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).
 2. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}.
-3. Navigate to **Connections > Sources** and select the **Reverse ETL** tab.
+3. Navigate to **Connections > Sources** then select the **Reverse ETL** tab.
 4. Click **+ Add Reverse ETL source**.
 5. Select **DB2** and click **Add Source**.
-6. Enter the configuration settings for your DB2 source:
+6. Fill in the DB2 connection settings:
   * Hostname: `<hostname>`
   * Port: `<port>`
   * Database: `<db_name>`
   * Username: `<segment_db2_user>`
   * Password: `<password>`
-  * Schema [optional]: If not specified, Segment will use the user’s default schema
 7. Click **Test Connection** to validate the setup.
 8. If the connection is successful, click **Add source**.
 
-After you've successfully added your DB2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.
+After successfully adding your DB2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.

From 11ab7804dada11d14383e7d49ea723e035a37716 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:38:12 -0400
Subject: [PATCH 07/25] Update src/_data/sidenav/main.yml

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 src/_data/sidenav/main.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
index d73e7ddb26..ca54f8f1a6 100644
--- a/src/_data/sidenav/main.yml
+++ b/src/_data/sidenav/main.yml
@@ -211,7 +211,7 @@ sections:
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup
         title: Databricks Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup
-        title: DB2 Reverse ETL Setup
+        title: Db2 Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup
         title: Postgres Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup

From 1dcbf58be15a0f67869105a34ee5ca012f1db4fc Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:38:30 -0400
Subject: [PATCH 08/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index f72827138d..031711f608 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -1,5 +1,5 @@
 ---
-title: DB2 Reverse ETL Setup
+title: Db2 Reverse ETL Setup
 ---
 
 Set up DB2 as your Reverse ETL source.

From 73240ca0b890fcd196e0c2a5e279588549e62f71 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:38:37 -0400
Subject: [PATCH 09/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 031711f608..f53e0dbf11 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -2,7 +2,7 @@
 title: Db2 Reverse ETL Setup
 ---
 
-Set up DB2 as your Reverse ETL source.
+Set up Db2 as your Reverse ETL source.
 
 At a high level, when you set up DB2 for Reverse ETL, the configured database user must have read permissions on any tables involved in the query, and write permissions on a managed schema (`SEGMENT_REVERSE_ETL`) that Segment uses to track sync progress. Authentication is handled through username and password credentials configured in the Segment app.
 

From 3c5c38c6e25a8de55a5d6fa715aa3beb65ceec78 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:38:48 -0400
Subject: [PATCH 10/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index f53e0dbf11..dfdc448ee8 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -4,7 +4,7 @@ title: Db2 Reverse ETL Setup
 
 Set up Db2 as your Reverse ETL source.
 
-At a high level, when you set up DB2 for Reverse ETL, the configured database user must have read permissions on any tables involved in the query, and write permissions on a managed schema (`SEGMENT_REVERSE_ETL`) that Segment uses to track sync progress. Authentication is handled through username and password credentials configured in the Segment app.
+At a high level, when you set up Db2 for Reverse ETL, the configured database user must have read permissions on any tables involved in the query and write permissions on a managed schema (`SEGMENT_REVERSE_ETL`) that Segment uses to track sync progress. Segment authenticates with your Db2 instance through a username and password. 
 
 
 

From 7086a9fe94d503c7b682a99a67f5534c117c2a4a Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:38:56 -0400
Subject: [PATCH 11/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index dfdc448ee8..a68b8b00ef 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -12,7 +12,7 @@ At a high level, when you set up Db2 for Reverse ETL, the configured database us
 
 In order to run a Reverse ETL sync in a DB2 warehouse, Segment needs the following permissions:
 
-* **Permission to read from all tables used in the model** (i.e., the tables included in your SELECT query).
+* **Permission to read from all tables used in the model**: The user must be able to access all tables included in your SELECT query.
 * **Permission to create and manage a schema** for tracking sync metadata.
 * **Permission to create tables in the database**, needed for internal metadata tables.
 

From fab1552266e19b0310e7e8ae756e36abbc916b9c Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:39:05 -0400
Subject: [PATCH 12/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index a68b8b00ef..662a6e6f63 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -10,7 +10,7 @@ At a high level, when you set up Db2 for Reverse ETL, the configured database us
 
 ## Required permissions
 
-In order to run a Reverse ETL sync in a DB2 warehouse, Segment needs the following permissions:
+In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user with the following permissions:
 
 * **Permission to read from all tables used in the model**: The user must be able to access all tables included in your SELECT query.
 * **Permission to create and manage a schema** for tracking sync metadata.

From b98e62f05b2862c4dc819fe293a95cb822f90fce Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:39:16 -0400
Subject: [PATCH 13/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 662a6e6f63..01a5974710 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -13,7 +13,7 @@ At a high level, when you set up Db2 for Reverse ETL, the configured database us
 In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user with the following permissions:
 
 * **Permission to read from all tables used in the model**: The user must be able to access all tables included in your SELECT query.
-* **Permission to create and manage a schema** for tracking sync metadata.
+* **Permission to create and manage a schema**: Segment creates and manages a schema in your warehouse to track sync metadata.
 * **Permission to create tables in the database**, needed for internal metadata tables.
 
 

From 395ae0fefa28cdaf5aed8bb891b2cca74c8ec7da Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:39:24 -0400
Subject: [PATCH 14/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 01a5974710..959a8b902d 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -14,7 +14,7 @@ In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user w
 
 * **Permission to read from all tables used in the model**: The user must be able to access all tables included in your SELECT query.
 * **Permission to create and manage a schema**: Segment creates and manages a schema in your warehouse to track sync metadata.
-* **Permission to create tables in the database**, needed for internal metadata tables.
+* **Permission to create tables in the database**: Segment creates metadata tables in your warehouse. 
 
 
 > info "Use a dedicated user for Segment"

From 41f68c771c412ceb6ffb2aa30e3b6c42475b50b0 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:39:42 -0400
Subject: [PATCH 15/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 959a8b902d..eb60c3e5b0 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -17,8 +17,8 @@ In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user w
 * **Permission to create tables in the database**: Segment creates metadata tables in your warehouse. 
 
 
-> info "Use a dedicated user for Segment"
-> It's recommended to create a dedicated DB2 user for Segment with access limited to only the relevant schemas and tables.
+> info "Create a dedicated user for Segment's Reverse ETL connection"
+> Segment recommends that you create a dedicated Db2 user for when setting up Reverse ETL. This user should only have access to the relevant schemas and tables you'll need to access during syncs between Segment and your warehouse. 
 
 1. In IBM Cloud, go to your DB2 instance and navigate to **Administration > User management**.
 2. Click **Add**.

From 67039972db0eac918f27c3ecc7616e363f2e8ae7 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:39:50 -0400
Subject: [PATCH 16/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index eb60c3e5b0..ea2ff2337f 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -20,7 +20,7 @@ In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user w
 > info "Create a dedicated user for Segment's Reverse ETL connection"
 > Segment recommends that you create a dedicated Db2 user for when setting up Reverse ETL. This user should only have access to the relevant schemas and tables you'll need to access during syncs between Segment and your warehouse. 
 
-1. In IBM Cloud, go to your DB2 instance and navigate to **Administration > User management**.
+1. In IBM Cloud, go to your Db2 instance and navigate to **Administration > User management**.
 2. Click **Add**.
 3. Create a new user with *user* privileges. Make sure to save the username and password—these are needed to configure the Segment
    source connection later.

From 7eeb28c122c1e15e2ea7ea90d5ef2ef1bb7f2970 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:40:16 -0400
Subject: [PATCH 17/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md   | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index ea2ff2337f..7bcb50b37f 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -22,8 +22,7 @@ In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user w
 
 1. In IBM Cloud, go to your Db2 instance and navigate to **Administration > User management**.
 2. Click **Add**.
-3. Create a new user with *user* privileges. Make sure to save the username and password—these are needed to configure the Segment
-   source connection later.
+3. Create a new user with *user* privileges. Note the username and password of the user you created, as you'll need this information to set up the Segment source connection in a later step. 
 
 
 > info ""

From 81e188c2ed96b3e71de71c654d498c960f6af1d7 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:40:33 -0400
Subject: [PATCH 18/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 7bcb50b37f..8cf7cd95cd 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -26,10 +26,10 @@ In order to run a Reverse ETL sync in your Db2 warehouse, you'll create a user w
 
 
 > info ""
-> The `SEGMENT_REVERSE_ETL` schema will be created and managed by Segment to track the status of each sync. 
+> Segment creates and manages the `SEGMENT_REVERSE_ETL` schema to track the status of each sync. 
 > You can also choose to create this schema yourself by running: 
 > `CREATE SCHEMA SEGMENT_REVERSE_ETL` 
-> Then grant Segment the appropriate privileges.
+> After you've created the schema, grant Segment the appropriate privileges.
 
 
 

From d8a752c819d8a68ed00b64eea85fe6d2d65a0d63 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:40:54 -0400
Subject: [PATCH 19/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 8cf7cd95cd..248c55cee4 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -48,7 +48,7 @@ GRANT SELECT ON TABLE <schema_name>.<table_name> TO USER <username>;
 ```
 
 
-## Set Up Guide
+## Set up guide
 
 To set up DB2 as your Reverse ETL source:
 

From b7b8003d9bf158be335ae3aadcc312a595dc033a Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:01 -0400
Subject: [PATCH 20/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 248c55cee4..5e63d4c5bb 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -50,7 +50,7 @@ GRANT SELECT ON TABLE <schema_name>.<table_name> TO USER <username>;
 
 ## Set up guide
 
-To set up DB2 as your Reverse ETL source:
+To set up Db2 as your Reverse ETL source:
 
 1. Make sure your DB2 database is network-accessible from [Segment's IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).
 2. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}.

From f1cb5598eca5e44802fb6932a0295d2fd1d9a663 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:15 -0400
Subject: [PATCH 21/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 5e63d4c5bb..1ad061f3e2 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -52,7 +52,7 @@ GRANT SELECT ON TABLE <schema_name>.<table_name> TO USER <username>;
 
 To set up Db2 as your Reverse ETL source:
 
-1. Make sure your DB2 database is network-accessible from [Segment's IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).
+1. Confirm that your Db2 database is network-accessible from the [IP address that Segment uses to connect to your warehouse](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).
 2. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}.
 3. Navigate to **Connections > Sources** then select the **Reverse ETL** tab.
 4. Click **+ Add Reverse ETL source**.

From c036ce8d840604c677259cead15bb00f10ab79d5 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:21 -0400
Subject: [PATCH 22/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 1ad061f3e2..a03f7d6582 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -56,7 +56,7 @@ To set up Db2 as your Reverse ETL source:
 2. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}.
 3. Navigate to **Connections > Sources** then select the **Reverse ETL** tab.
 4. Click **+ Add Reverse ETL source**.
-5. Select **DB2** and click **Add Source**.
+5. Select **Db2** and click **Add Source**.
 6. Fill in the DB2 connection settings:
   * Hostname: `<hostname>`
   * Port: `<port>`

From 66ee83d3d9b95d7d483d2c0f970826bf46fd38b9 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:27 -0400
Subject: [PATCH 23/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index a03f7d6582..8571b40a44 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -57,7 +57,7 @@ To set up Db2 as your Reverse ETL source:
 3. Navigate to **Connections > Sources** then select the **Reverse ETL** tab.
 4. Click **+ Add Reverse ETL source**.
 5. Select **Db2** and click **Add Source**.
-6. Fill in the DB2 connection settings:
+6. Fill in the following Db2 connection settings:
   * Hostname: `<hostname>`
   * Port: `<port>`
   * Database: `<db_name>`

From d11879789358fcbc92cb57813bc7fc0367b92d45 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:37 -0400
Subject: [PATCH 24/25] Update
 src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 .../reverse-etl/reverse-etl-source-setup-guides/db2-setup.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
index 8571b40a44..915a9d71bc 100644
--- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
+++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md
@@ -66,4 +66,4 @@ To set up Db2 as your Reverse ETL source:
 7. Click **Test Connection** to validate the setup.
 8. If the connection is successful, click **Add source**.
 
-After successfully adding your DB2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.
+After successfully adding your Db2 source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.

From f1a05db2061d4b5ae4c1da87f3ac22bebba18bf0 Mon Sep 17 00:00:00 2001
From: Gil Omer <80776787+gilsegment@users.noreply.github.com>
Date: Wed, 11 Jun 2025 10:41:44 -0400
Subject: [PATCH 25/25] Update src/connections/reverse-etl/setup.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
---
 src/connections/reverse-etl/setup.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md
index 88cf060cd7..4172e6e281 100644
--- a/src/connections/reverse-etl/setup.md
+++ b/src/connections/reverse-etl/setup.md
@@ -28,7 +28,7 @@ To add your warehouse as a source:
   - [Azure Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup)
   - [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup)
   - [Databricks Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup)
-  - [DB2 Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup)
+  - [Db2 Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup)
   - [Postgres Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup)
   - [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup)
   - [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup)