Home/ Questions/Q 4270630
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T07:19:57+00:00

My system was mentioned in this question: https://stackoverflow.com/questions/5633634/best-index-strategies-for-read-only-table because the data is readonly, and

  • 0

My system was mentioned in this question:

https://stackoverflow.com/questions/5633634/best-index-strategies-for-read-only-table

because the data is readonly, and in specific time, a part of data (50-200k rows, about 200 byte/each) is intensively queried, so I think allowing client to connect to database and query each row/query is way too expensive. It would be a better choice if I cache part of data (which is being intensively queried) into RAM, which is much faster than SQL Server.

The problem is, the system I’m currently working on is a webservice, so I’m not sure that it allows large static data to be cached. Is my idea a good choice? How my data can “survive” when IIS recycle?

Thank you very much.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Load the data into RAM on Application_Start event. Then you don’t need to worry about IIS restart

    Here is an MS guide about Caching Data at Application Startup

    • 0