Quantcast
Channel: Primary Key choice on table with unique identifier - Database Administrators Stack Exchange
Browsing all 5 articles
Browse latest View live

Answer by David Spillett for Primary Key choice on table with unique identifier

As your API is build around the UUID being the key for these rows you are stuck with that as your functional primary key at this point, though that in itself is not a bad thing. Clustering on a UUID...

View Article



Answer by Solomon Rutzky for Primary Key choice on table with unique identifier

There are a few things to consider here:How is data most often looked up in this table?How is data most often sorted in this table?Does this table relate to others as the parent record (i.e. will other...

View Article

Answer by Greenstone Walker for Primary Key choice on table with unique...

Consider the [Date] or [Created] column for a clustered, non-unique, index key (especially if they are increasing columns) and keep the [TypeID] column as a non-clustered, unique, key.Clustered index...

View Article

Answer by ODU90DBA for Primary Key choice on table with unique identifier

Although I don't work in Azure I would certainly suggest, for SQL Server to use a sequentially, incrementing key like newsequentialid but since you say that Azure doesn't support it... following...

View Article

Primary Key choice on table with unique identifier

I'm reconsidering my choice of Primary Key on a table, and would like some input.Some context: We are building a REST API, where clients access "Assets" identified by a GUID. So, the table for Asset in...

View Article

Browsing all 5 articles
Browse latest View live




Latest Images