VICIfast
ENES
Guides & tutorials

Keep the call log small: log archiving on a busy VICIdial database

Why VICIdial's log tables slow a busy database as they grow, what log archiving moves, how to check it runs, and when to schedule it.

VICIfast Support
··3 min read
A modern call-centre office — illustration for: Keep the call log small: log archiving on a busy VICIdial database
Photo by MART PRODUCTION on Pexels

Nobody decides to keep three years of call history in the live database. It just happens. Every Lead you dial, every answer, every status change adds rows to VICIdial's log tables, and unless something moves the old ones out, they stay.

On a quiet system you'd never notice. On a busy one, the size of those tables sets how long each read on them takes, and that sets how long your floor waits.

Why a big log slows everything around it

VICIdial's call records live in MyISAM tables, and nothing can write to a MyISAM table while a read on it is still running. A read with more rows to get through holds the lock longer. Every Disposition (the status an agent picks when a call ends) and every call hand-off queued behind it waits that much longer.

On one floor we looked at, the log tables had grown to 7 to 12.5 million rows each. Nobody had ever archived them.

We also tested whether a bigger machine would help. Replaying a live floor's database traffic at up to seven times its normal pace, the database never needed more than 3.1 of its cores. The slow moments came from table locks on the call log. At that size the answer is a smaller call log, not a bigger database machine; the replay results show each step.

In a cluster this matters even more, because one database and web server answers every dialer. Our VICIdial cluster guide explains that layout.

What log archiving moves, and what it leaves

VICIdial ships a script for the job, ADMIN_archive_log_tables.pl. It moves old rows out of the live log tables into archive tables, so the tables your floor reads and writes all day hold only recent history.

Nothing is thrown away. Most VICIdial reports have a Search archived data option that reads the archive tables, so a manager can still pull last year's numbers. Running a report against archived data covers that checkbox.

VICIdial also has an optional Cold-Storage DB Server setting, which lets some old log archives be read from a separate database server instead of the main one.

Archiving the log tables doesn't touch your Call recording audio. Recordings are files, not rows in these tables, and they need their own retention plan.

flowchart LR
  A[Dialers and agent screens] --> B[(Live log tables)]
  B --> C[Archive script, off shift]
  C --> D[(Archive tables)]
  E[Everyday reports] --> B
  F[Search archived data] --> D

Check whether yours runs

You don't need database access to find out. Open Admin, then System Settings, and find Oldest Logs Date. It's a display-only field showing the oldest log date that hasn't been archived.

If that date sits inside the history your managers actually report on, archiving is doing its job. If it's the week the server went live, it has never run.

Scheduling it on a busy database

Run the script on a schedule, not once. One clean-up helps until the tables grow back, and on a busy floor they always do.

Pick a time when nobody is dialing. Moving millions of rows is heavy work on the very tables the floor uses, and a live shift will feel it.

Midnight isn't always quiet. A nightly job that archives the log of agent screen Latency (the delay between an agent's browser and the server) froze one floor for 17 seconds at midnight. If you dial late or around the clock, schedule archiving for your real low point, not the clock's.

To decide how much history stays live, ask what your managers report on week to week. Anything older can sit in the archive, where the floor never waits on it.

On one server the same schedule works, and our plans cover floors that still fit on one machine. On the clusters we run, we hunt down whatever holds the call tables during a shift, and a log nobody has archived is on that list.

When the floor needs a database machine of its own, book a sizing call and see today's cluster prices.

Frequently asked

› Does log archiving delete call history?
No. Old rows move into archive tables, and most VICIdial reports can still read them with the Search archived data option.
› Will a bigger database server fix a slow call log?
Not at the sizes we have measured. In our replay the database never needed more than 3.1 of its cores; the slow moments came from table locks, and a smaller log shortens those.
› How often should the archive script run?
On a regular schedule, at a time when nobody is dialing. A one-off clean-up helps for a while, then the tables grow back.

About VICIfast

We run VICIdial servers for call centres, so you don’t have to. You get the dialer set up, secured and kept running — we handle the server, the updates and the backups. Bring your own phone carrier at no markup, or use VICIfast Voice, our own US calling and numbers, from $0.0085 a minute. From $49 a month per server.

Questions? Call +1 636 556 0022 and talk to someone who runs dialers.

Citing this article

VICIfast Engineering. “Keep the call log small: log archiving on a busy VICIdial database”. VICIfast LLC, November 22, 2026. Retrieved from https://vicifast.com/blog/vicidial-log-archiving-busy-database

Have questions?

Related posts

You might be interested in

Comments

Comments are reviewed before they appear. We never publish your email.

No comments yet - be the first.