---
title: QueryUserAssignmentLog
---

The `QueryUserAssignmentLog` table contains the history of user assignments for [Persistent Query replicas](../../performance/pq-redundancy.md#replicas) in the controller.

When a client first authenticates to the controller, it is assigned a replica slot for each Persistent Query that uses replicas, which tells it which copy of the Persistent Query to connect to. These replica slot assignments can change depending on the status of the Persistent Queries. Each replica slot assignment event generates a row in this table.

## Columns

| Column Name    | Column Type | Description                                                                                                                                |
| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `Date`         | String      | The date on which the information was generated. This is the partitioning column.                                                          |
| `Timestamp`    | Instant     | The timestamp of the event.                                                                                                                |
| `QuerySerial`  | long        | The Persistent Query's serial number.                                                                                                      |
| `QueryOwner`   | String      | The Persistent Query's owner.                                                                                                              |
| `AdminGroups`  | String      | Additional administrators for the Persistent Query (i.e., users or groups that can edit, start, stop, or delete the query).                |
| `AssignedSlot` | int         | The replica slot the user is assigned for this Persistent Query.                                                                           |
| `User`         | String      | The user being assigned the slot.                                                                                                          |
| `PolicyName`   | String      | The [replica assignment policy](../../performance/pq-redundancy.md#assignment-policies) such as `RoundRobin`.                              |
| `Details`      | String      | The reason for the assignment. Examples from the `RoundRobin` policy include `First Assignment` and `Rebalancing due to reduced capacity`. |
| `IsReset`      | Boolean     | Whether or not the query is reset (i.e. all replicas are removed).                                                                         |

## Related documentation

- [Internal tables overview](./internal-tables.md)
- [`AuditEventLog`](./audit-event-log.md)
- [`PersistentQueryConfigurationLog`](./persistent-query-configuration-log.md)
- [`PersistentQueryStateLog`](./persistent-query-state-log.md)
- [`ProcessEventLogIndex`](./process-event-log-index.md)
- [`ProcessEventLog`](./process-event-log.md)
- [`ProcessInfo`](./process-info.md)
- [`ProcessMetrics`](./process-metrics.md)
- [`QueryOperationPerformanceLogCoreV2Index`](./query-operation-performance-log-index.md)
- [`QueryOperationPerformanceLogCoreV2`](./query-operation-performance-log.md)
- [`QueryPerformanceLogCoreV2`](./query-performance-log.md)
- [`ResourceUtilization`](./resource-utilization.md)
- [`ServerStateLogIndex`](./server-state-log-index.md)
- [`ServerStateLog`](./server-state-log.md)
- [`UpdatePerformanceLogCoreV2Index`](./update-performance-log-core-index.md)
- [`UpdatePerformanceLogCoreV2`](./update-performance-log-core.md)
- [`WorkspaceDataSnapshot`](./workspace-data-snapshot.md)
- [`WorkspaceData`](./workspace-data.md)