July 29, 2014 at 12:05 pm
HI Guy
The question is a bit allover
- What are your thoughts on adding clustered index on datetime (createdDate , native GUID) column.
The data will be be physically organized in the clustered index allowing range operations to perform its duties. But will the GUID column make any impact ( drawbacks) should it be made part of the clustered key ?
The GUID column will provide the lookup with the required indexes to support.
- Any of you using COMPGuids for the clustered indexes.
All suggestions/thoughts are appreciated.
Cheers
Jude
July 29, 2014 at 12:42 pm
The only reason to add the GUID to the clustered index is to make it unique...is that the reason for adding this column to the clustered index.
I GENERALLY prefer to add an identity field as a clustering index and then have separate indexes on other columns like date added. You can still perform range scans on the indexes.
July 29, 2014 at 3:47 pm
Yep, totally agree. I come from the school of thought, but things change with sharded databases.
The question i posted is of two folds. one to sort out a existing problem and other to sort out upcoming design issue.
July 30, 2014 at 1:01 am
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply