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 7588569
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T19:57:16+00:00 2026-05-30T19:57:16+00:00

We have a database that is currently 1.5TB in size and grows by a

  • 0

We have a database that is currently 1.5TB in size and grows by a gigabyte worth of data every day (a text file) that is 5 million records – and it grows daily

It has many columns, but a notable one is START_TIME which has the date and time –

We run many queries against a date range –

We keep 90 days worth of records inside of our database, and we have a larger table which has ALL of the records –

Queries run against the 90 days worth of records are pretty fast, etc. but queries run against ALL of the data are slow –

I am looking for some very high level answers, best practices

We are THINKING about upgrading to SQL Server enterprise and using table partitioning, and splitting the partition based on month (12) or days (31)

Whats the best way to do this?

Virtual Physical, a SAN, how many disks, how many partitions, etc. –

Sas

  • 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-30T19:57:17+00:00Added an answer on May 30, 2026 at 7:57 pm

    You don’t want to split by day, because you will touch all partitions every month. Partitioning allows you not to touch certain data.

    Why do you want to partition? Can you clearly articulate why? If not (which I assume) you shouldn’t do it. Partitioning does not improve performance per-se. It improves performance in some scenarios and it takes performance in others.

    You need to understand what you gain and what you loose. Here is what you gain:

    • Fast deletion of whole partitions
    • Read-Only partitions can run on a different backup-schedule

    Here is what you loose:

    • Productivity
    • Standard Edition
    • Lower performance for non-aligned queries (in general)

    Here is what stays the same:

    • Performance for partition-aligned queries and indexes

    If you want to partition, you will probably want to do it on date or month, but in a continuous way. So don’t make your key month(date). Make it (year(date) + ‘-‘ + month(date)). Never touch old partitions again.

    If your old partitions are truly read-only, put each of them in a read-only file-group and exclude it from backup. That will give you really fast backup and smaller backups.

    Because you only keep 90 days of data you probably want to have one partition per day. Every day at midnight you kill the last partition and alter the partition function to make room for a new day.

    There is not enough information here to answer anything about hardware.

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

Sidebar

Related Questions

I have a database that contains data for many clients. Currently, we insert tens
I currently have a DetailsView in ASP.NET that gets data from the database based
I have a database of names of people that has (currently) 35 million rows.
I have a Sql Server 2008 Express database file that's currently being used by
I currently have a simple database program that reads keys in from a text
I have a database that is currently sharded. This is the first time that
I have a database issue that i currently cannot wrap my head around with
I currently have a database that gets updated from a legacy application. I'd like
I have a database with DateTime fields that are currently stored in local time.
I currently have a Postgres 8.4 database that contains a varchar(10000) column. I'd like

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.