Been there, done that. The ERP system at my previous job, though it was SQL Server-based, did not use the transaction log: they had an application server that did everything there via RBAR. No stored procedures. They did have a couple of views, IIRC. Why listen to a DBA with 20+ years experience when you've got slick salesmen?

The system slowed as the mountain of data grew, we produced all sorts of charts and graphs showing that the DB server was underutilized but application response was still slow. The answer from the vendor? Buy a faster DB server. So they're probably replacing that server every 2-3 years even though it's not being significantly taxed.

When they implemented an upgrade to the utility billing system and claimed that it now used the transaction log properly, I suggested creating a copy of everything, starting a cycle, then pulling the plug to see if it recovered gracefully and accurately. The ERP manager went almost apoplectic on the spot. Needless to say it didn't happen.

I'm not sure if I've ever been happier leaving a job. Not only does that vendor's package name not appear on my resume, but if I ever interview with someone who does use that system, I'll walk. I will never work with that POS again. A friend of mine who worked with it as the OS sysadmin and security admin (their own system, not SQL Server security) is of the same opinion.