Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6150331
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T19:35:59+00:00 2026-05-23T19:35:59+00:00

I have a large temp table (~160 million rows) #itemsTemp itemId | style |

  • 0

I have a large temp table (~160 million rows) #itemsTemp

itemId  | style    | styleWeight
--------------------------------
int     | smallint | float(53)

and the following query on it:

select 
    itemId,
    style,
    SUM(styleWeight) itemCount 
from 
    #itemsTemp 
group by itemId,style

Currently #itemsTemp has no indexes. I’m a little confused about what would be best here:

  1. A composite index on itemId and style (and probably include styleWeight)
  2. Separate indexes on itemId and style

Which way should I go? Why? Any other options?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T19:36:00+00:00Added an answer on May 23, 2026 at 7:36 pm

    Composite index on itemId and style with styleWeight included would be the best option.

    This will allow Stream Aggregate without sorting and/or clustered seek/RID lookup overhead.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have large database table, approximately 5GB, now I wan to getCurrentSnapshot of Database
I have a very large set of data (~3 million records) which needs to
I have a large (multi-GB) data file exported from an Oracle table. I want
Hi I have a large list of data: http://paste-it.net/public/y17027d/ It is 67859 rows by
We are using SQL Server 2008 Enterprise version. We have a large table FooTable
I have the following PLSQL functions that returns following error when returning a large
I have large data sets (10 Hz data, so 864k points per 24 Hours)
I have large batches of XHTML files that are manually updated. During the review
I have large images displayed in a grouped tableview. I would like the images
In my application I have large area (≈5000x5000pts) and I must allow user to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.