StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGood Database-Design has no identity-columns in the tables, right?
primarykey
Id
1647136
data
AcceptedAnswerId
1647137
AnswerCount
2
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2009-10-28T22:11:17.260
FavoriteCount
1
LastActivityDate
2014-04-17T17:42:49.223
LastEditDate
2009-10-30T21:03:34.910
LastEditorUserId
3043
OwnerUserId
124675
ParentId
0
PostTypeId
1
Score
1
ViewCount
2187
LastEditorDisplayName
text
Body
<p>what is the benefit of having an additional identity column in each table of a database? What are the drawbacks?</p> <p>Update: Now i want to expand the case and introduce replication. What for is this surogate key (identity comlumn) aside of the rowguid we get with the replication. Behalf of K. Brian Kelley's objection one should set the clustered index on this rowguid (and forget the identity-column). WHat do you think?</p>
Tags
<database><sql-server-2008>
Title
Good Database-Design has no identity-columns in the tables, right?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJoel Coehoorn
UserOwnerUserId
1. USIce
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POGood Database-Design has no identity-columns in the tables, right?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POGood Database-Design has no identity-columns in the tables, right?
  UserUserId
  USAvery Payne
  VoteTypeVoteTypeId
  VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.