# amfelt sql

Work with the SQL Amfelt generates for your warehouse.

Write out the SQL Amfelt generates from your data contracts and project
configuration, and check that what is written still matches. The files land in
your own repository, so they are reviewed, versioned and diffed like any other
source you own.

These files are for reading. They are generated for review rather than for
execution, and running one directly would write placeholder values into your
warehouse. To change the SQL Amfelt generates, customize the template it comes
from with `amfelt template eject`.

## Usage

```text
amfelt sql [command] [flags]
```

## Global flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--amfelt-dir` | `string` | `.amfelt` | directory for workspace files (such as plugins); does not move agent identity (controlled by AMFELT_DIR) |
| `--config` | `string` | — | directory or filename of the application configuration |
| `-f`, `--format` | `string` | `default` | log format to use; either default, pretty, or json |
| `-l`, `--level` | `string` | `info` | minimum log level to display; either error, warn, info, or debug |
| `-v`, `--verbose` | `bool` | `false` | trigger to use verbose logging |
{.clidoc-flags-table}

## Subcommands

- [`sql check`](/docs/reference/command-line/sql-check/)
- [`sql generate`](/docs/reference/command-line/sql-generate/)

---

Generated from `amfelt` v5.6.3.