# Configure a database request default

Request defaults in Coordinator DB are saved for a selected database. They are not per-user profiles. Before changing one, confirm the intended database and inspect the effective current value.

```sql
SELECT name, value, type
FROM system.settings
WHERE name = 'max_result_rows'
FORMAT csv;
```

A supported persisted change uses `SET`:

```sql
SET max_result_rows = 10000;
```

## Understand the scope

The change requires autocommit with no active transactions in that database. Other connected clients observe committed settings before later requests. Resource limits are sampled at request start; a SET inside a multi-statement request changes defaults for later requests rather than the active request's budget.

A nonzero server XML ceiling remains effective when it is stricter. Read `system.settings` for the effective value and `main.settings` for a saved value when investigating the difference.

## Choose the right interface

Only documented SET names are accepted. Connection flags and database-header values use PRAGMA or validated catalog writes. Format options such as CSV delimiters use the statement's `SETTINGS` clause and do not persist. Credential changes belong to the users XML file and require a restart.

See [SET reference](https://coordinatordb.com/docs/reference/statements/set), [database settings](https://coordinatordb.com/docs/reference/settings/session-settings) and [server ceilings](https://coordinatordb.com/docs/concepts/features/configuration/settings/constraints-on-settings).