i recall reading that guid cause write to be spread to many B-tree pages. This cause most page to be mostly empty (fragmented) wasting space and slowing query.

i recall reading that guid cause write to be spread to many B-tree pages. This cause most page to be mostly empty (fragmented) wasting space and slowing query. Also once pages start to fill the majority of insert would cause page split instead of having an amortized cost... Ideally you should use pseudo-sequential ID. By having an counter per partition and using <Counter>+<partition key> as your table primary key