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.
demographics. Every time a user>-----Original Message-----
>I have a user table which is to store user'smore and more time>signs up, one row will be created.
>When this table grows (say, 50M rows now), it is takingway).>to generate reports from that table (if that is the onlysure...I want the>
>I am thinking a work-around for this but I am not verylike there is no other>experts here to give me some inputs:
>The basic idea is to keep the user table grow...seemsthat table)>way to get around it..(no duplicate users allowed forinsert it to a>But I have a sp to summarize the report for each day andlook at the report>report table. So when I do the reporting I just need tomore.>table and no need to get that from the user table any>
>Let me know what you think.