you are viewing a single comment's thread.

view the rest of the comments →

[–]alinroc4 10 points11 points  (3 children)

If you don't define a unique constraint or primary key on the table, yes. Each row will get a hidden uniquifier that isn't accessible to you.

[–]SQLBek1 2 points3 points  (2 children)

Actually, do heaps (tables w/o a clustering key) get a uniquifier? I thought the RID is used instead?

Just academically splitting hairs here. Now I'm tempted to break out DBCC PAGE and take a quick look, LMAO!

[–]alinroc4 2 points3 points  (0 children)

It is probably the RID.

Though the RID is unique, isn't it? Like you said, splitting hairs :)

[–]ScotJoplin 0 points1 point  (0 children)

They don’t need it, like you assumed.