Page 1 of 1

Max Rows for mysql?

PostPosted: Tue Jun 24, 2008 1:22 pm
by chuckford
We have a lot of calls cycling through our system. The call_log and the vicidial_log are both getting rather large. Is there a max row count that I should let it get to, before deleting some records?

Will having to much in either of these tables start to cause problems for the reps?

Thanks

PostPosted: Tue Jun 24, 2008 2:28 pm
by pylinuxian
the lighter your db the faster is your server, ... thats the law of gravity I guess ... Files on Disk get larger, files in memory too ... procedures take longer to execute ... solution ?
move long periode reporting task from production server to a new one by creating a script to copy data over from production to history server ... many commercial apps do actually this under the hood in a scheduled task at night, they copy data over to new tables called xxxx_hst & free production tables, reporting tools are configured to look at the xxxx_hst tables if you enter older dates.

PostPosted: Wed Jun 25, 2008 3:28 am
by mflorell
The limit is pretty big. I have had hundreds of millions of records in the call log table before, but I would not recommend that.

You should purge or backup logs after a certain amount of time(depending on your call volume and need).