Amazon QuickSight is excited to announce the launch of Unique Key for Dataset, enabling users to define additional aspects of their data semantics. The unique key will be used to improve performance for QuickSight visuals, especially un-aggregated table charts. Previously, to maintain table pagination stability, all columns in the table visual were sorted, which was an expensive query causing performance latency. Now, with the unique key defined in the dataset, once the column is used in the visual, users will automatically experience improved sorting performance without compromising user behavior. For some cases, the new approach can increase the performance up to 60% decrease of the visual rendering time. For further details, visit here.
The new Unique Key for Dataset feature is now available in Amazon QuickSight Enterprise Editions in all QuickSight regions - US East (N. Virginia and Ohio), US West (Oregon), Canada, Sao Paulo, Europe (Frankfurt, Stockholm, Paris, Ireland and London), Asia Pacific (Mumbai, Seoul, Singapore, Sydney and Tokyo), and the AWS GovCloud (US-West) Region.
Hello, I’m trying to understand the ‘unique key’, in other systems/context such as redshift, is this the equivalent of a sort key / partition key? Just checking as the name might be confused with a primary key. Thanks!
In Amazon Redshift, primary and unique keys are informational only—they are not enforced as constraints. (Reference: Table constraints - Amazon Redshift)
As such, there is no strict equivalent to constraint-enforced keys found in other RDBMSs like Oracle, where unique keys are used to enforce data integrity (Unique Key).
In QuickSight, defining a column as a unique key signals that it contains distinct values. This enables optimization during sorting operations: QuickSight can use that column exclusively for sorting, reducing processing time. Note that once data is sorted by a column with unique values, further sorting has no effect, as the row order is already uniquely determined.
