Tag Info

New answers tagged

0

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 keys don't have to be unique - SQL Server will add a uniquifier to non-unique values. As long as most of the values are distinct, this shouldn't noticably ...


0

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 Kimberly Tripp's advice on http://www.sqlskills.com/blogs/kimberly/guids-as-primary-keys-andor-the-clustering-key/ The identity seems to be the better choice to ...



Top 50 recent answers are included