How many fields, is too many in a table? - InfoPath Dev
in

InfoPath Dev

How many fields, is too many in a table?

Last post 09-01-2005 09:58 AM by Greg Collins. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 08-25-2005 06:34 AM

    How many fields, is too many in a table?

    I'm using Access to create my database, and I wanted to be sure that I don't have too many fields in a table. I know tables with many fields increase the time Access takes to process information. I have created relationships between tables. I have seven tables, one of the tables contains 20 fields. Is this too many?

    Chantel.
  • 09-01-2005 09:58 AM In reply to

    Re: How many fields, is too many in a table?

    This is not an easy to answer question. It mainly depends on your performance requirements. If 20 fields makes performance slow to a crawl then it is too many.

    The bigger issue is not the number for fields (columns) but the number of rows returned. If you have 20 fields with 10 rows, performance should be just fine. But if you have 20 fields with 100,000 rows, chances are you'll be waiting a while for the view to be displayed, and performance within the form will not be that great.

    There's really not one set answer. But I can tell you that the number of rows will have a bigger affect on performance than the number of fields (columns).

    Greg Collins [InfoPath MVP]
    InfoPath Dev
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.