StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy this Query takes such a long time to execute
primarykey
Id
12051342
data
AcceptedAnswerId
12051741
AnswerCount
2
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2012-08-21T08:54:16.683
FavoriteCount
0
LastActivityDate
2012-08-21T09:16:43.103
LastEditDate
2012-08-21T09:02:54.757
LastEditorUserId
1105514
OwnerUserId
1150594
ParentId
0
PostTypeId
1
Score
2
ViewCount
159
LastEditorDisplayName
text
Body
I have three tables <ul> <li>glSalesJournal</li> <li>HMISAdd</li> <li>HMISMain</li> </ul> Now what i am trying to do is add the glSalesJournal amt with HMISAdd amt while grouping up with various Fields and inserting the result into glSalesJournal The glSalesJournal contains 633173 records The HMISAdd contains 4193 records HMISAdd and glSalesJournal contains the same columns which are <ul> <li>loc</li> <li>glAcct</li> <li>glSubAcct</li> <li>batchNbr</li> <li>contractNbr</li> <li>amt</li> </ul> I added indexes to the table still the results are the same. Here is my code: <pre><code>INSERT INTO hmismain (loc, glacct, subacct, batchnbr, contractnbr, amt) SELECT glsalesjournal.loc, glsalesjournal.glacct, glsalesjournal.glsubacct, ( glsalesjournal.amt + hmisadd.amt ) AS sumAmt, glsalesjournal.batchnbr, glsalesjournal.salescontnbr FROM glsalesjournal LEFT OUTER JOIN hmisadd ON ( glsalesjournal.loc = hmisadd.loc AND glsalesjournal.glacct = hmisadd.glacct AND glsalesjournal.glsubacct = hmisadd.subacct AND glsalesjournal.batchnbr = hmisadd.batchnbr AND glsalesjournal.salescontnbr = hmisadd.contractnbr ) GROUP BY glsalesjournal.loc, hmisadd.loc, glsalesjournal.glacct, hmisadd.glacct, glsalesjournal.glsubacct, hmisadd.subacct, glsalesjournal.batchnbr, hmisadd.batchnbr, glsalesjournal.salescontnbr, hmisadd.contractnbr </code></pre> The time taken by the script to execute is more than 2 hours. Even when I limit the Records to 100 the time taken is the same. Can someone please guide me how can I optimize the script. Thanks
Tags
<mysql><query-optimization>
Title
Why this Query takes such a long time to execute
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAdi
UserOwnerUserId
1. USAnkit Suhail
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
 POWhy this Query takes such a long time to execute
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhy this Query takes such a long time to execute
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.