StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1341522
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-27T14:34:26.370
FavoriteCount
0
LastActivityDate
2009-08-27T14:34:26.370
LastEditDate
LastEditorUserId
0
OwnerUserId
13302
ParentId
1341393
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
Heaps are just tables without a clustering key - without a key that enforces a certain physical order. I would not really recommend having heaps at any time - except maybe if you use a table temporarily to bulk-load an external file, and then distribute those rows to other tables. In every other case, I would strongly recommend using a clustering key. SQL Server will use the Primary Key as the clustering key by default - which is a good choice, in most cases. UNLESS you use a GUID (UNIQUEIDENTIFIER) as your primary key, in which case using that as your clustering key is a horrible idea. See Kimberly Tripp's excellent blog posts <a href="http://www.sqlskills.com/BLOGS/KIMBERLY/post/GUIDs-as-PRIMARY-KEYs-andor-the-clustering-key.aspx" rel="noreferrer">GUIDs as Primary and/or the clustering key</a> and <a href="http://www.sqlskills.com/BLOGS/KIMBERLY/post/The-Clustered-Index-Debate-Continues.aspx" rel="noreferrer">The Clustered Index Debate Continues</a> for excellent explanations why you should always have a clustering key, and why a GUID is a horrible clustering key. My recommendation would be: <ul> <li>in 99% of all cases try to use a <code>INT IDENTITY</code> as your primary key and let SQL Server make that the clustering key as well</li> <li>exception #1: if you're bulk loading huge data amounts, you might be fine without a primary / clustering key for your temporary table</li> <li>exception #2: if you must use a GUID as your primary key, then set your clustering key to a different column - preferably a <code>INT IDENTITY</code> - and I would even create a separate INT column just for that purpose, if no other column can be used</li> </ul> Marc
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSQL Server heap v.s. clustered index
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmarc_s
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. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.