---
title: "Amplia Reg command: **update-db**"
description: "Amplia Reg command update-db: applies the database model migrations when running without db_owner privileges, using a privileged connection string."
canonical: "https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/tool/update-db"
locale: "en"
product: "Amplia Reg"
last_updated: "2026-07-14"
---

# Amplia Reg command: **update-db**

## Name

`update-db` - Updates the database model

## Syntax

```sh
dotnet Lacuna.AmpliaRegNg.Site.dll [settings] -- update-db
```

Or, on Docker:

```sh
docker run -i lacunasoftware/ampliareg:3.0 [settings] -- update-db
```

The `settings` arguments are additional settings to overwrite settings from configuration files and environment variables,
for instance `--Section1:Name1=value1 --Section2:Name2=value2`.

## Description

The `update-db` command updates the database model by applying a series of *migrations*. It is meant to be used only when
[running Amplia without db_owner privileges](https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/unprivileged-db-user).

Since in this scenario Amplia's database credentials do not grant permissions to change the database model, you typically
will want to run this command passing a **privileged connection string**:

```sh
dotnet Lacuna.AmpliaRegNg.Site.dll --ConnectionStrings:DefaultConnection="Data Source=SERVER;Initial Catalog=DATABASE;User ID=USERNAME;Password=PASSWORD" -- update-db
```

> **Tip**
>
> On Linux, if your password contains the `!` character, use single quotes instead, e.g. `--ConnectionStrings:DefaultConnection='...'`, to avoid
> shell history expansions

## See also

* [Amplia Reg command-line tool](https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/tool)
* [Running Amplia Reg without db_owner privileges](https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/unprivileged-db-user)