Reputation
478
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 6 17
Impact
~50k people reached

  • 0 posts edited
  • 3 helpful flags
  • 19 votes cast
Aug
19
revised Should the index on an identity column be nonclustered?
edited title
Aug
17
revised Should the index on an identity column be nonclustered?
added 100 characters in body
Aug
17
revised Should the index on an identity column be nonclustered?
added 74 characters in body
Aug
17
awarded  Nice Question
Aug
13
revised Should the index on an identity column be nonclustered?
added 287 characters in body
Aug
3
revised Should the index on an identity column be nonclustered?
added 79 characters in body
Aug
3
revised Should the index on an identity column be nonclustered?
added 25 characters in body
Aug
3
revised Should the index on an identity column be nonclustered?
added 16 characters in body
Aug
3
comment Should the index on an identity column be nonclustered?
@ypercube In my question, the query I listed is the common one. The ID is more like a surrogate key. It may be only used to join another table. I want to find out which case, CI or non-CI is better in my case.
Aug
3
revised Should the index on an identity column be nonclustered?
added 22 characters in body
Aug
3
revised Should the index on an identity column be nonclustered?
added 70 characters in body
Aug
3
comment Should the index on an identity column be nonclustered?
@ypercube The link kejser.org/clustered-indexes-vs-heaps said that the non-CI will have less LIO.
Aug
3
revised Should the index on an identity column be nonclustered?
added 2 characters in body
Aug
3
asked Should the index on an identity column be nonclustered?
Jul
27
awarded  Caucus
Jul
24
awarded  Notable Question
Jul
10
awarded  Popular Question
Jun
30
awarded  Popular Question
Jun
23
awarded  Notable Question
Apr
14
revised Grant Windows logins to read a secondary database of log shipping?
added 65 characters in body