Databases — dodil vbase db

The db commands are the control-plane tier: they talk to the Dodil gateway to allocate, list, select, and delete serverless databases. They map directly onto the Databases API.

db create

Allocates a new serverless database in your organization.

dodil vbase db create product-search

Database product-search created.
ID: svc-7f3a9c2e

Allocation is asynchronous — the database is returned in CREATING state and becomes connectable once it reaches RUNNING. Capture the printed ID; it is the service_id you pass to db use and db drop. Run db list to watch the status.

--org <id> overrides the organization from your config.

db list

Lists the databases in your organization with their status.

dodil vbase db list

ID            Name             Status    DRN
svc-7f3a9c2e  product-search   RUNNING   drn:dodil:vbase:svc-7f3a9c2e

Wait until Status is RUNNING before connecting. Add -o json for the full service objects.

db use

Resolves a database’s connection details and writes them into your CLI config, so the Milvus-direct commands know where to connect.

dodil vbase db use svc-7f3a9c2e

Switched to database 'svc-7f3a9c2e' at endpoint product-search.vbase.dev.dodil.io:443

Under the hood this calls GetServiceAccess and writes the returned endpoint, port, and db_name to the vbase scope of ~/.config/unified-cli/config.yaml:

vbase:
  host: product-search.vbase.dev.dodil.io
  port: 443
  db_name: db_7f3a9c2e
  service_name: svc-7f3a9c2e

This is what lets collection, data, index, and status run without endpoint flags — they read this active context. Run db use again any time you switch databases.

db use only sets your local context. The actual collections, indexes, and vectors live in Milvus — see Connecting with the Milvus SDK if you want to connect from your own application code instead of the CLI.

db drop

Deletes a database by its service_id.

dodil vbase db drop svc-7f3a9c2e

Database svc-7f3a9c2e dropped.

This is destructive — the database and its collections are removed. The service moves through DELETING to DELETED.

db test-grpc

A diagnostic that dials the gateway over gRPC (TLS on :443) and lists your databases, to confirm gateway connectivity and auth independently of the HTTP path.

dodil vbase db test-grpc

Dialing Gateway via gRPC at api.dev.dodil.io:443...
Successfully called ListServices via Gateway gRPC!
 - ID: svc-7f3a9c2e, Name: product-search

Use it when db commands fail and you want to isolate a transport vs auth problem.

See also

• Collections, Data & Index — the Milvus-direct commands that run after db use.
• Databases API — the allocate → poll → access flow these commands wrap.
• Gaps & Troubleshooting — config resolution and common errors.