> ## Documentation Index > Fetch the complete documentation index at: https://planetscale.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # PlanetScale CLI commands: database ## Getting Started Make sure to first [set up your PlanetScale developer environment](/cli/planetscale-environment-setup). Once you've installed the `pscale` CLI, you can interact with PlanetScale and manage your databases straight from the command line. ## The `database` command This command allows you to create, read, delete, dump, and restore databases. **Usage:** ```bash theme={null} pscale database ``` ### Available sub-commands | **Sub-command** | **Sub-command flags** | **Description** | **Product** | | :------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------- | :--------------- | | `create ` | `--region `, `--plan `, `--cluster_size `, `--major-version `, `--min-storage `, `--max-storage ` | Create a database with the specified name | Postgres, Vitess | | `delete ` | `--force` | Delete the specified database | Postgres, Vitess | | `dump ` | `--local-addr
`, `--output `, `--tables `, `--columns `, `--threads (defaults to 16)` | Backup and dump the specified database | Vitess | | `list ` | | List all databases in the current org | Postgres, Vitess | | `restore-dump ` | `--dir `\*, `--local-addr
`, `--overwrite-tables`, `--threads (defaults to 1)`, `--allow-different-destination`, `--show-details`, `--schema-only`, `--data-only`, `--starting-table `, `--ending-table ` | Restore the specified database from a local dump directory | Postgres, Vitess | | `show ` | `--web` | Retrieve information about a database | Postgres, Vitess | > \* *Flag is required* #### Sub-command flag descriptions Some of the sub-commands have additional flags unique to the sub-command. This section covers what each of those does. See the above table for which context. | **Sub-command flag** | **Description** | **Applicable sub-commands** | | :------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------- | | `--region` | Specify the [region](/vitess/regions) of the new database. Default is `us-east`. | `create` | | `--plan` | Specify the plan for the database. Currently, `scaler_pro` is the only option and the default. | `create` | | `--cluster_size` | For Base plan databases, you may specify the cluster size. Default is `PS_10` | `create` | | `--major-version` | The major version of the database (Postgres only). Currently supports `17` or `18`. | `create` | | `--min-storage` | Minimum storage size in bytes for Postgres databases using Amazon Elastic Block Storage (EBS). | `create` | | `--max-storage` | Maximum storage size in bytes for Postgres databases using Amazon Elastic Block Storage (EBS). | `create` | | `--force` | Delete a database without confirmation. | `delete` | | `--local-addr
` | Local address to bind and listen for connections. By default the proxy binds to 127.0.0.1 with a random port. | `dump`, `restore-dump` | | `--threads` | Number of concurrent threads to use | `dump`, `restore-dump` | | `--output ` | Output directory of the dump. By default the dump is saved to a folder in the current directory. | `dump` | | `--tables ` | Comma separated string of tables to dump. By default, all tables are dumped. | `dump` | | `--columns ` | Specify which columns to include when dumping specific tables. Use format `table:col1,col2`. Can be specified multiple times. | `dump` | | `--wheres string` | Comma separated string of WHERE clauses to filter the tables to dump. | `dump` | | `--replica` | Dump from a replica (if available; will fail if not). | `dump` | | `--rdonly` | Dump from a rdonly tablet (if available; will fail if not). | `dump` | | `--keyspace ` | Optionally target a specific keyspace to be dumped. Useful for sharded databases. | `dump` | | `--shard ` | Optional shard to target, must be used with keyspace | `dump` | | `--output-format ` | Output format for the dump. Options: `sql` (default), `json`, `csv`. | `dump` | | `--dir ` | Directory containing the files to be used for the restore. | `restore-dump` | | `--overwrite-tables` | If true, will attempt to DROP TABLE before restoring. | `restore-dump` | | `--allow-different-destination` | If true, will allow you to restore the files to a database with a different name without needing to rename the existing dump's files. | `restore-dump` | | `--show-details` | If true, will add extra output during the restore process. | `restore-dump` | | `--schema-only` | If true, will only restore the schema files during the restore process. | `restore-dump` | | `--data-only` | If true, will only restore the data files during the restore process. | `restore-dump` | | `--starting-table ` | Table to start from for the restore (useful for restarting from a certain point) | `restore-dump` | | `--ending-table ` | Table to end at for the restore (useful for stopping restore at a certain point) | `restore-dump` | | `--web` | Perform the action in your web browser | `show` | ### Available flags | **Flag** | **Description** | | :-------------------------- | :----------------------------------------------------------- | | `-h`, `--help` | Get help with the `database` command | | `--org ` | Specify the organization for the database you're acting upon | ### Global flags | **Command** | **Description** | | :------------------------------ | :----------------------------------------------------------------------------------- | | `--api-token ` | The API token to use for authenticating against the PlanetScale API. | | `--api-url ` | The base URL for the PlanetScale API. Default is `https://api.planetscale.com/`. | | `--config ` | Config file. Default is `$HOME/.config/planetscale/pscale.yml`. | | `--debug` | Enable debug mode. | | `-f`, `--format ` | Show output in a specific format. Possible values: `human` (default), `json`, `csv`. | | `--no-color` | Disable color output. | | `--service-token ` | The service token for authenticating. | | `--service-token-id ` | The service token ID for authenticating. | The `--format` flag does not apply to the database dump files created by the `dump` subcommand. However, you can control the output format using the `--output-format` flag, which supports SQL (default), JSON, and CSV formats. When using SQL format, dumps are compatible with [mydumper](https://github.com/mydumper/mydumper). ## Examples ### Create a new `scaler_pro` database **Command:** ```bash theme={null} pscale database create new-database --region --plan scaler_pro --cluster_size PS_80 ``` **Output:** Database `new-database` was successfully created. ### Create a Postgres database with storage size settings (Amazon EBS) Use `--min-storage` and `--max-storage` to set the initial and maximum storage size in bytes when creating a Postgres database on Amazon Elastic Block Storage (EBS). **Command:** ```bash theme={null} pscale database create new-postgres-db --engine postgres --region --min-storage 10737418240 --max-storage 21474836480 ``` In this example, the database starts at 10 GiB (`10737418240` bytes) and can scale up to 20 GiB (`21474836480` bytes). ### Create a dump of an existing branch: This command is only available for Vitess databases. For Postgres databases, use the [pg\_dump](https://www.postgresql.org/docs/current/app-pgdump.html) command instead. **Command:** ```bash theme={null} pscale database dump --output="" --org="" ``` **Output:** A local export of your database will be generated within the current directory by default but since we are providing an `--output` location above that will be used instead. ### Export data in different formats: You can specify the output format when dumping your Vitess database using the `--output-format` flag: **Export as JSON:** ```bash theme={null} pscale database dump --output-format=json ``` **Export as CSV:** ```bash theme={null} pscale database dump --output-format=csv ``` **Export as SQL (default):** ```bash theme={null} pscale database dump --output-format=sql ``` ### Dump specific columns from tables: You can use the `--columns` flag to export only specific columns from your tables. This is useful when you need a partial export or want to exclude sensitive data: ```bash theme={null} # Export only specific columns from multiple tables pscale database dump --columns 'users:id,name' --columns 'orders:id,total' ``` The schema dump will include the complete table schema, but the data files will only contain the specified columns. ### Restore a backup to an existing branch: **Command:** ```bash theme={null} pscale database restore-dump --dir="" --org="" ``` **Output:** You should receive output indicating the restore is progressing until it completes successfully. The command above will allow you to restore an existing backup to another branch located either within the same organization/database as the original, or within a completely different organization/database. As of `pscale` v0.218.0 or newer the `--allow-different-destination` flag is now available. If this flag is provided it will make the steps below about renaming the files unnecessary. If you opt to import into a database with a different name you will have to make sure you rename the files from your backup beforehand. For example, the files will be named something like this: ```bash theme={null} .-schema.sql ``` And you will want to rename all of the files in the dump folder to have the new database name if it is not the same as the existing one: ```bash theme={null} .-schema.sql ``` If importing into a branch that already contains table definitions that you want to overwrite, you may also be required to pass in the optional `--overwrite-tables` flag. ## Need help? Get help from [the PlanetScale Support team](https://planetscale.com/contact?initial=support), or join our [Discord community](https://pscale.link/community) to see how others are using PlanetScale.