---
title: "AlloyDB"
slug: "alloydb"
description: "Connect Dataddo to AlloyDB and load data from any source with insert, upsert, or truncate write modes. No coding required."
tags: ["Data warehouse", "Data destination", "How-to guide"]
updated: 2026-07-26T12:55:51Z
published: 2026-07-26T12:55:51Z
canonical: "docs.dataddo.com/alloydb"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AlloyDB

AlloyDB is a fully managed, PostgreSQL-compatible database service that's designed for your most demanding workloads, including hybrid transactional and analytical processing. AlloyDB pairs a Google-built database engine with a cloud-based, multi-node architecture to deliver enterprise-grade performance, reliability, and availability.

## Authorize Connection to AlloyDB

### Prerequisites

- A running AlloyDB instance reachable by Dataddo. If you use a firewall, allow the [Dataddo IPs](/docs/network-acl).
- A database user with rights to create tables and to insert, update, and delete rows in the target schema.

### Create the authorizer

In Authorizers, click Authorize New Service and select AlloyDB, then fill in the fields:

| Field | Description |
| --- | --- |
| A name for this authorizer in Dataddo | A label so you can recognize the connection later. |
| Server IP or Hostname | Public IP or Hostname of your AlloyDB Server. |
| Database | Name of the database you will use for writing or reading the data. |
| Username | Username for authentication. |
| Password | Password for authentication. |
| Port | Port to connect to AlloyDB. The default value is 5432. |
| TLS/SSL Settings | Keep the value on PREFER, this will ensure the SSL connection when available. If you want to enforce SSL without a fallback to unencrypted connection, use REQUIRED. Default: `verify-full`. |
| Use SSH tunnel | In case you need to connect via SSH tunnel, create it first on the Security setting page and use pick it here afterwards. |

Click Save. Dataddo validates the connection.

## Create an AlloyDB Destination

Go to Destinations, click Create Destination, and select AlloyDB. Give the destination a name, choose the authorizer, and click Save.

## Write Modes

The write mode decides how each flow run changes the target table. AlloyDB offers the standard set below, and the default is `insert`. Which modes are available, and whether you can switch modes on an existing flow, can depend on the table's current state.

| Mode | Meaning | Composite Key |
| --- | --- | --- |
| `insert` | Appends new rows on every run. | No |
| `insert_ignore` | Appends rows, skipping rows that already exist. | Yes |
| `truncate_insert` | Empties the table, then writes the current data. | No |
| `upsert` | Inserts new rows and updates existing rows matched by the Composite Key. | Yes |
| `update` | Updates existing rows matched by the Composite Key; fails rows with no match. | Yes |
| `update_ignore` | Updates matched rows, skipping rows with no match. | Yes |
| `delete` | Deletes rows matched by the Composite Key. | Yes |

### Composite Key

The Composite Key is the set of columns whose combined values identify each row. Every mode except `insert` and `truncate_insert` needs one. You can select up to 4 columns.

## Table Naming

Dataddo creates the table on the first write if it does not exist. When you name the table:

- Table name: table name should contains only letters, numbers underscores or dashes.
- You can put date-range patterns such as `{{1d1}}` in the table name.

## How to Create a Flow to AlloyDB

1. Go to Flows and click Create Flow.
2. Add one or more sources.
3. Add AlloyDB as the destination and pick the authorizer.
4. Choose a write mode, and a Composite Key for modes that need one.
5. Set the schema and the table name.
6. Set the schedule and click Save.

## Troubleshooting

### Invalid schema or table name

The schema or table name does not match AlloyDB's naming rules. Fix the name in the flow to match the rules in Table Naming, then restart the flow.

### Insufficient privileges

The database user cannot create tables or write rows in the target schema. Grant the user create, insert, update, and delete rights, then restart the flow.

### Cannot connect to AlloyDB

Dataddo cannot reach AlloyDB. Check the credentials in the authorizer, and make sure the server is reachable by Dataddo. If you use a firewall, allow the [Dataddo IPs](/docs/network-acl).

## Related Articles

- [Data Backfilling to Storages](https://docs.dataddo.com/docs/data-backfilling-to-storages)
- [Write Modes](https://docs.dataddo.com/docs/data-storages#write-modes)
- [Implementation of Batch Ingestion to Data Warehouses](https://docs.dataddo.com/docs/ingestion-to-data-warehouses)
- [Network Access Control List (ACL) Configuration](https://docs.dataddo.com/docs/network-acl)
- [SSH Tunnelling](https://docs.dataddo.com/docs/ssh-tunnelling)
- [Data Transformations](https://docs.dataddo.com/docs/data-transformations)
- [Data Quality Firewall](https://docs.dataddo.com/docs/data-quality-firewall)