Re: ADO.NET performance with large tables
- From: Nico Callewaert <NicoCallewaert@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 23 Jul 2005 01:45:03 -0700
Thanks for the replies !
I know you can limit the rows by using a SELECT query. But lets say a
customer table. The user wants to see a list of the customers. I cannot say
to my user : "the list is limited to only the customers starting with "A".
Of course he wants to see all customers. Same for quotations for example.
If I will tell my user : "the list is limited to quotations of the last 3
months", it will be weird. All users want a list represented in a datagrid
that is easy to scroll. But I realize that the more rows that will be in a
table, the slower the application will become.
Could you provide me with some good design practices ?
Many thanks in advance again !
Nico Callewaert
.
- Follow-Ups:
- Re: ADO.NET performance with large tables
- From: William \(Bill\) Vaughn
- Re: ADO.NET performance with large tables
- Prev by Date: RE: Oracle Computed column datatype
- Next by Date: Re: ADO.NET performance with large tables
- Previous by thread: Re: ADO.NET performance with large tables
- Next by thread: Re: ADO.NET performance with large tables
- Index(es):
Relevant Pages
|
|