Home/ Questions/Q 6784785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T17:02:29+00:00

I have an ASP.NET MVC 3 application with a SQL Server 2005 database backend.

  • 0

I have an ASP.NET MVC 3 application with a SQL Server 2005 database backend. It is linked to the database using LINQ to SQL. On certain instances, the database will get updated by the application, but sometimes it still caches old data that should not be getting cached.

For example, if the user fills out a form to post a BlogEntryComment (one of my LINQ to SQL types), it will get added to the database. But, the new BlogEntryComment won’t show up in my views that request it. In addition, if I remove a BlogEntryComment, it still shows up in the views. Here is what I have determined about this behavior:

  • It is not caused by browser caching. I have cleared the cache; tried simutaneously on different browsers and different computers; to no avail.

  • It is not happening with “top-level” types, like my BlogEntry type. It is happening with types like BlogEntryComment that have a relationship (one BlogEntry to many comments) with my “top-level” types.

  • If I restart the server, or try it on a different server, it seems to clear whatever cache it is in, and I don’t get erroneous results.

  • It will eventually show the updated data, but it takes up to 15 minutes for it to finally appear.

I have tried to turn off every kind of cache options that I have been able to find in Web.config:

...
<system.web>
    ...
    <caching>
        <outputCache enableOutputCache="false" enableFragmentCache="false">
        </outputCache>
    </caching>
    <httpRuntime enableKernelOutputCache="false" />
</system.web>
<system.webServer>
    ...
    <caching enabled="false">
    </caching>
</system.webServer>
...

…but with no luck. Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Check out the documentation for l2s DataContext. Its meant to be short lived – i.e. create and dispose every http request. If it’s static as you describe, it’ll live as long as the app domain does.

    What’s most likely happening is that your DC is staying in memory and subsequent requests for data are not going to the db. After 15 minutes or whatever, your app domain recycles, and you get a fresh DC, and fresh data.

    • 0