Home/ Questions/Q 6318179
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T15:36:38+00:00

If I am using a SqlConnection, apparently the best practice is to dispose of

  • 0

If I am using a SqlConnection, apparently the best practice is to dispose of it ASAP, and let the connection pooling handle the details. Should I follow the same pattern when I am using System.Data.Linq.DataContext?

Should I create my context once and pass it along to my methods, or should I get the connection string from my config file and create the contexts multiple times and save on passing the parameters?

Edit: A useful link about identity maps: Architecting LINQ To SQL Applications, part 7

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should keep a data context around only as long as necessary to perform an operation.

    The reason for this is that it uses something called an Identity Map so that every time you select say customer 1 you get the same object back. This means it is holding lots of references and will consume more and more memory over time and these results will become increasingly stale.

    In the case of a web app it is common to create one per request and the DataContext class is optimised for quick creation.

    • 0