Bruce Gilham Jr.

All work · Media & entertainment

Record Research Inc.

Decades of Billboard chart data moved off SQL Server 7, Classic ASP and Visual FoxPro onto Azure, while the books kept getting published.

Years
2025–now
Sector
Publishing — chart data
Role
Sole developer and architect
Outcome
Still running

What was wrong

A music-chart publisher's entire archive lived on SQL Server 7, a Classic ASP application and Visual FoxPro book-generation tools — a stack nobody could hire for and hardware that would not last. The business ran on it every day, so it could not be taken down to be replaced.

What I built

Restored the old backups into Azure SQL, rebuilt the legacy application for the cloud with user and admin security on Entra ID, and kept the FoxPro book-generation tools running against the new database throughout. Built a data validator that pulls chart data from an outside scraped source, transforms it to the publisher's own conventions, and shows an editor exactly what will be written before anything goes to production. Used an LLM to reverse-engineer legacy records with a confidence score on each and statistical sampling to verify rather than trust.

What happened

Live on Azure. Along the way the validator found that weeks-at-peak figures had been silently inflated for years — a data error nobody knew they had.

Stack

Classic ASP Visual FoxPro SQL Server 7 Azure SQL Azure App Service Blazor C# PostgreSQL Entra ID AI-assisted migration

Have a system like this one?

Tell me what it does, what it is written in, and what breaks when it goes down. I will say plainly whether I can help.

Tell me what it runs on