dcsimg
www.webdeveloper.com
Results 1 to 4 of 4

Thread: Rows vs. Columns

  1. #1
    Join Date
    Jun 2009
    Posts
    5

    Rows vs. Columns

    Which database would be better?

    200k rows, 25 columns

    OR

    2 million rows, 2 columns

    I'll probably have to access the one with 2 million rows twice as often. My thought is #1 based on my assumption that accessing the right row slows down the process more than other tasks.

  2. #2
    Join Date
    Jun 2009
    Posts
    36
    Performance-wise, it doesn't really matter if your queries will use an index. 2 million rows using an index will be significantly faster than 200k rows without an index. But with no index, 200k of course will be faster.
    Last edited by triassic; 06-26-2009 at 03:31 PM.

  3. #3
    Join Date
    Jun 2009
    Posts
    5
    Either one would use an index. Is there a point where the number of rows on the larger row table would run slower than the larger column table? Or with an index would that put their speed always in the same spot?

    The larger row table will always have roughly 10x the rows as the larger column table. Columns are static.

  4. #4
    Join Date
    Jun 2009
    Posts
    36
    I'm no DB expert, but with indexes, 200k vs 2mil isn't going to make any difference. As for number of columns, I don't see how more would make a difference.

    You can always run some tests, see what happens.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center



Recent Articles