Re: ADO.NET performance with large tables

Thank you very much for the help !!

Nico

"William (Bill) Vaughn" wrote:

> 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
>
>
>
.

Relevant Pages

  • Re: Attitude to defects
    ... By paying attention to these lists when scheduling ... Developers don't need to distinguish though: ... Don't waste effort on separating the sheep and goats, ... Customers don't care _why_ something doesn't work, ...
    (comp.software.testing)
  • Re: ADO.NET performance with large tables
    ... William (Bill) Vaughn ... > I have a similar problem but instead of customers it's parts. ... > serveral MS-Access tables. ... >> reasonable lists. ...
    (microsoft.public.data.ado)
  • Re: Adding Customer Contact Emails to Address List
    ... customers aliases, so if they want to email only three or thirty at a time, ... the customer's email aliases are there. ... their own distribution lists if they want to.. ... Open the public folder and switch the view to "By ...
    (microsoft.public.windows.server.sbs)
  • RE: SharePoint Portal Architecture
    ... I've been working with SharePoint for over 3 years and I still refer to this ... > CarInfo - a list of information on a bunch of different cars (model, ... > Our customers will subscribe to the CarInfo but not automatically all ... > several different custom lists per customer. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: redesign of a database
    ... To generate your card list each of your employees you could simply generate a report based on a query which lists all their selected contacts, which is fine as a paper reference of each employee's recommendations, but you also need to store the recommendations in a separate CardList table so that this can be added to cumulatively with each employee's recommendations. ... FROM Customers INNER JOIN Contacts ...
    (microsoft.public.access.gettingstarted)