Professional Web Applications Themes

How to deal with huge table? - Microsoft SQL / MS SQL Server

I have a user table which is to store user's demographics. Every time a user signs up, one row will be created. When this table grows (say, 50M rows now), it is taking more and more time to generate reports from that table (if that is the only way). I am thinking a work-around for this but I am not very sure...I want the experts here to give me some inputs: The basic idea is to keep the user table grow...seems like there is no other way to get around it..(no duplicate users allowed for that table) But I have ...

  1. #1

    Default How to deal with huge table?

    I have a user table which is to store user's demographics. Every time a user
    signs up, one row will be created.
    When this table grows (say, 50M rows now), it is taking more and more time
    to generate reports from that table (if that is the only way).

    I am thinking a work-around for this but I am not very sure...I want the
    experts here to give me some inputs:
    The basic idea is to keep the user table grow...seems like there is no other
    way to get around it..(no duplicate users allowed for that table)
    But I have a sp to summarize the report for each day and insert it to a
    report table. So when I do the reporting I just need to look at the report
    table and no need to get that from the user table any more.

    Let me know what you think.

    Thank you,
    TH


    T H Guest

  2. #2

    Default How to deal with huge table?

    As long as there is no need for the most current data then
    that should be an acceptable solution.

    There are other options, but they get complex and
    expensive. The other thing I would look at is your stored
    procedures. Make sure they are optimized. A poorly
    written procedure may work ok when the table is smaller
    but can kill the system as the volume of data grows.
    >-----Original Message-----
    >I have a user table which is to store user's
    demographics. Every time a user
    >signs up, one row will be created.
    >When this table grows (say, 50M rows now), it is taking
    more and more time
    >to generate reports from that table (if that is the only
    way).
    >
    >I am thinking a work-around for this but I am not very
    sure...I want the
    >experts here to give me some inputs:
    >The basic idea is to keep the user table grow...seems
    like there is no other
    >way to get around it..(no duplicate users allowed for
    that table)
    >But I have a sp to summarize the report for each day and
    insert it to a
    >report table. So when I do the reporting I just need to
    look at the report
    >table and no need to get that from the user table any
    more.
    >
    >Let me know what you think.
    >
    >Thank you,
    >TH
    >
    >
    >.
    >
    DJoe Guest

Similar Threads

  1. loading only few rows from huge table
    By Mark in forum PostgreSQL / PGSQL
    Replies: 2
    Last Post: December 29th, 05:38 PM
  2. wtf is the deal?
    By Tom in forum PERL Miscellaneous
    Replies: 32
    Last Post: September 25th, 04:03 PM
  3. Replies: 3
    Last Post: September 18th, 04:55 PM
  4. DBI problem : How can I load quickly one huge table with DBI ??.
    By Tim Haynes in forum PERL Miscellaneous
    Replies: 3
    Last Post: September 13th, 03:43 AM
  5. Replies: 2
    Last Post: August 12th, 07:55 AM

Bookmarks

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139