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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T05:09:38+00:00 2026-05-16T05:09:38+00:00

We have a database on a server with enough RAM to hold the entire

  • 0

We have a database on a server with enough RAM to hold the entire db. Is there any merit and/or drawbacks to preloading the data into memory after a long period of inactivity?

Other factors during this nightly process:
Balance data are recreated from another app/database/server.
Indexes and stats get refreshed
full backup to disk

then data would be preloaded.

  • 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-16T05:09:39+00:00Added an answer on May 16, 2026 at 5:09 am

    If you have enough memory to hold the entire DB in it, you might as well do that, in particular if the server has no other responsibilities and will not require the RAM for anything else.

    The advantage is that now fetching will not have to go to the hard drives (and even with SSDs, RAM is faster).

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

Sidebar

Related Questions

We have a SQL server database. To manipulate the data non-programmatically, I can use
We have a database (SQL Server 2005) which we would like to get under
We have SQL Server database setup. We are setting up a replication scenarios where
We have a production SQL Server 2005 database server with the production version of
Our database server is a SQL 2008 server. My colleagues all have XP service
We have a production web and database server with SQL Server 2000. (However, a
I have been looking at the new database server we are setting up for
Generally the database server is the biggest, most expensive box we have to buy
We are moving our database server to a bigger box. I have several databases
I have an SQL server database that I am querying and I only want

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.