Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">15.5.5</button>

- [15.5.5](https://docs.cloud.google.com/alloydb/omni/containers/15.5.5/docs/store-embeddings.md.txt)

<br />

This page shows you how to use AlloyDB as a vector database with the `vector` extension that includes `pgvector` functions and operators. These functions and operators let you store embeddings as vector values.

<br />

## Required database extension

Use the `vector` extension, version `0.5.0.google-1` or later, which includes
`pgvector` functions and operators, to store generated embeddings as `vector` values. This
is a version of `pgvector` that Google has extended with optimizations specific
to AlloyDB.

```sql
CREATE EXTENSION IF NOT EXISTS vector;
```

## Store generated embeddings

Ensure that you have already created a table in your AlloyDB database.

> [!NOTE]
> **Note:** If your application uses the LangChain framework and your dataset has `O(100k)` embeddings, we recommend that you use the `AlloyDBVectorStore` vector class included in the AlloyDB LangChain library to store your embeddings. For more information, see [Build LLM-powered applications using
> LangChain](https://docs.cloud.google.com/alloydb/docs/ai/langchain#vector_store_procedure_guide).

To store vector embeddings, do the following:

1. Create a `vector[]` column in your table to store your embeddings:

   ```sql
   ALTER TABLE TABLE ADD COLUMN EMBEDDING_COLUMN vector(DIMENSIONS);
   ```

   Replace the following:
   - `TABLE`: the table name

   - `EMBEDDING_COLUMN`: the name of the new embedding column

   - `DIMENSIONS`: the number of dimensions that the model
     supports.

     For example, if you are using one of the `textembedding-gecko`English models---for example, `textembedding-gecko@003` with Vertex AI, specify `768`.
2. Copy the vectors to the vector column. The following example assumes your embeddings are available in a `CSV` file:

   ```sql
   COPY TABLE (EMBEDDING_COLUMN) FROM 'PATH_TO_VECTOR_CSV (FORMAT CSV);
   ```

   Replace the following:
   - `PATH_TO_VECTOR_CSV`: the full path of where you have stored your `CSV` file.

> [!WARNING]
>
> **Preview
> --- AlloyDB ScaNN index**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

After you store the embeddings, you can use the `vector` extension or the `alloydb_scann`
extension to create indexes for faster query performance.

## What's next

- [Create indexes and query vectors](https://docs.cloud.google.com/alloydb/omni/containers/15.5.5/docs/store-index-query-vectors.md.txt)
- [An example embedding workflow](https://docs.cloud.google.com/alloydb/omni/containers/15.5.5/docs/example-embeddings.md.txt)