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

  • Home
  • SEARCH
  • 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 6219147
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T07:43:45+00:00 2026-05-24T07:43:45+00:00

I have a query that is run once per minute, on multiple tables (with

  • 0

I have a query that is run once per minute, on multiple tables (with joins). The largest table has 31 million rows after being used for about 18 months.
Generally the query is fast (< 1 second), except in cases where we have to go back a few months or more in time (order by datetime field descending, group by, top 1), then it can take up to 20 seconds.

I’ve started looking at partitioning. Now I read twice that partitioning does not increase query performance, instead it decreases performance, but it was twice by the same person (here and here). Is this correct?

  • 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-24T07:43:46+00:00Added an answer on May 24, 2026 at 7:43 am

    No partitioning does not necessarily decrease query performance.

    What you are describing sounds like being caused by parameter sniffing. Are your indexes and statistics up to date?

    Update (in response to comment): Ensure you have a regular index maintenance task scheduled.

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

Sidebar

Related Questions

I have a query that I run once a day that takes certain tables
I have a query that has 7 inner joins (because a lot of the
I have heard that Linq query write once can be run on SQL and
I have a SQL query that takes a very long time to run on
I have an update query being run by a cron task that's timing out.
I have a query that returns a bunch of rows. But using the same
I have the following code that should, when run, update a table of victims
I have a script that appends some rows to a table. One of the
i am useing the query below, when i run this query once per page
I have a query that is dynamically built after looking up a field list

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.