StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORDBS when to use complex indexes for queries and when use simple?
primarykey
Id
876723
data
AcceptedAnswerId
876730
AnswerCount
3
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-05-18T08:23:48.187
FavoriteCount
0
LastActivityDate
2009-05-18T08:55:29.760
LastEditDate
2009-05-18T08:48:08.370
LastEditorUserId
104014
OwnerUserId
104014
ParentId
0
PostTypeId
1
Score
1
ViewCount
304
LastEditorDisplayName
text
Body
<p>Suppose I have table in my DB schema called TEST with fields (id, name, address, phone, comments). Now, I know that I'm going to perform a large set of different queries for that table, therefore my question is next, when and why I shall create indexes like ID_NAME_INDX (index for id and name) and when it's more efficient to create separately index for id and index for name field(by when I mean for what type of query)?</p>
Tags
<sql><performance><indexing><rdbms>
Title
RDBS when to use complex indexes for queries and when use simple?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USArtem Barger
UserOwnerUserId
1. USArtem Barger
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
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PORDBS when to use complex indexes for queries and when use simple?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. CODo u mean that the ID may be repeated (Not unique) so u need to avoide redundancy for ID and Name fields?
  singulars
  PostPostId
  PORDBS when to use complex indexes for queries and when use simple?
  UserUserId
  USAhmy
2. CONo I mean, that I'm able to create index for name and index for id field or instead I can create one index for both fields together. So I'm asking which approach will be more efficient and for which type of queries.
  singulars
  PostPostId
  PORDBS when to use complex indexes for queries and when use simple?
  UserUserId
  USArtem Barger

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.