StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9424260
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-02-24T01:49:11.527
FavoriteCount
0
LastActivityDate
2012-02-24T09:52:37.423
LastEditDate
2012-02-24T09:52:37.423
LastEditorUserId
71059
OwnerUserId
1229744
ParentId
7579
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
Doing a <code>REORGANIZE</code> and then a <code>REBUILD</code> on the same indexes is pointless, as any changes by the <code>REORGANIZE</code> would be lost by doing the <code>REBUILD</code>. Worse than that is that in the maintenance plan diagram from SSW, it performs a <code>SHRINK</code> first, which fragments the indexes as a side effect of the way it releases space. Then the <code>REBUILD</code> allocates more space to the database files again as working space during the <code>REBUILD</code> operation. <ul> <li><code>REORGANIZE</code> is an online operation that defragments leaf pages in a clustered or non-clustered index page by page using little extra working space.</li> <li><code>REBUILD</code> is an online operation in Enterprise editions, offline in other editions, and uses as much extra working space again as the index size. It creates a new copy of the index and then drops the old one, thus getting rid of fragmentation. Statistics are recomputed by default as part of this operation, but that can be disabled.</li> </ul> See <a href="http://msdn.microsoft.com/en-us/library/ms189858.aspx" rel="noreferrer">Reorganizing and Rebuilding Indexes</a> for more information. Don't use <code>SHRINK</code> except with the <code>TRUNCATEONLY</code> option and even then if the file will grow again then you should think hard as to whether it's necessary: <a href="http://www.sqlservercentral.com/articles/SHRINKFILE/71414/" rel="noreferrer">sqlservercentral_SHRINKFILE</a> 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReorganise index vs Rebuild Index in Sql Server Maintenance plan
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAakashM
UserOwnerUserId
1. USLlew
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POReorganise index vs Rebuild Index in Sql Server Maintenance plan
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.