Re: Table bloat in Linq-SQL
- From: Jon Skeet [C# MVP] <skeet@xxxxxxxxx>
- Date: Sat, 10 Nov 2007 21:39:27 -0000
Andrus <kobruleht2@xxxxxx> wrote:
var db = new MyDb(connString);
causes creation of all objects corresponding to all tables in database.
Database contains 500 tables.
Application accesses only few tables at a time.
Creating large number of objects which are not used is bad design.
How to force Linq-SQL to create table objects only when they are first
accessed ?
You could partition your database into several contexts. Are you sure
this is actually an issue for you though? How much memory are you
seeing being used?
--
Jon Skeet - <skeet@xxxxxxxxx>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
.
- Follow-Ups:
- Re: Table bloat in Linq-SQL
- From: Andrus
- Re: Table bloat in Linq-SQL
- References:
- Table bloat in Linq-SQL
- From: Andrus
- Table bloat in Linq-SQL
- Prev by Date: Table bloat in Linq-SQL
- Next by Date: Re: difference c# 2.0 C# 3.0
- Previous by thread: Table bloat in Linq-SQL
- Next by thread: Re: Table bloat in Linq-SQL
- Index(es):
Relevant Pages
|
