Re: ADO.NET performance with large tables
- From: "William \(Bill\) Vaughn" <billvaNoSpam@xxxxxxxxx>
- Date: Sat, 23 Jul 2005 09:57:38 -0700
When users are trained properly, they understand that they have to ask for
reasonable lists. They are accustomed to doing this everywhere they
search--in the yellow pages, in Google, or in a library card index. When
they're looking for a pizza place do they start looking at the "As" in the
phone book? A good design helps them search by providing pre-filled filter
pick lists: County, Zip, State, region or the last 20 customers the user
worked with.
You can permit open-ended lists, but if you do, fetch 20-30 rows at a time
showing a page and when the user pages down, fetching the next 20--like
Google does when you search for "Home Loans".
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Nico Callewaert" <NicoCallewaert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:6962E1B5-7CF7-49A6-841B-93201D580405@xxxxxxxxxxxxxxxx
> 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: Nico Callewaert
- Re: ADO.NET performance with large tables
- References:
- Re: ADO.NET performance with large tables
- From: Nico Callewaert
- Re: ADO.NET performance with large tables
- Prev by Date: Re: ADO.NET performance with large tables
- Next by Date: Re: Copying access objects using .net
- Previous by thread: Re: ADO.NET performance with large tables
- Next by thread: Re: ADO.NET performance with large tables
- Index(es):
Relevant Pages
|
|