How Can We Improve This Old Access-Based Software for a Client?

0
8
Asked By TechWhiz99 On

I work at a managed service provider (MSP), and we have a client still using an outdated, on-premises Access-based program. This software is notorious for database instability, with tables getting corrupted weekly. The situation is complicated by the fact that the software only runs on Windows Server 2012 R2, and updating it isn't an option because the newer version won't work. The single virtual machine (VM) running this software struggles under peak hours, with 30 remote desktop sessions operating simultaneously. I've explored cloud solutions but found them too costly given that this server needs to run 24/7 with no downtime. When the VM crashes, it leads to chaos. I'm looking for availability solutions, either on-premises or temporary cloud options, but I'm unsure where to start. Any ideas would be appreciated! Thanks!

5 Answers

Answered By RiskManagementWiz On

Sounds like this solution really needs a major overhaul. Sure, it’ll cost money, but you should outline the potential losses from constant outages. This can show the client how crucial it is to invest in a modern solution, whether it’s finding a SaaS option or building a new application altogether.

CostlyConsult -

That's true! If they can't afford a big project now, maybe show them a simple app that uses fewer resources to reduce costs.

MigrationMaven -

Yeah, without updates, their situation is just going to deteriorate further.

Answered By LogicalLarry On

To be honest, you might want to compile a list of all the issues related to this software and link them to business risks. They probably think keeping you on is cheaper, but if you’re available 24/7 to fix issues, that adds up. Do they even know how much those disruptions cost them?

MoneyMatters -

Great point! You also need to clarify any contractual obligations and what happens if the situation spirals out of control.

JackTheCalculator -

Absolutely! If they don’t agree to a real migration, you should consider ending the partnership.

Answered By SysAdminSam On

If firing the client isn't an option, think about setting up a VM cluster. It might help with both capacity and availability. Just a heads-up, though, this won't patch the database corruption problem you’re facing with Access in the long run.

PragmaticTechie -

Exactly! Migrating off Access is really the only permanent fix.

ClientWhisperer -

They already had major issues before. It's a ticking time bomb waiting to go off!

Answered By ConsultantChris On

I've had clients in similar predicaments before. Instead of ditching them, I found a developer through Upwork to switch their app from Access to SQL Express for about $500. It greatly improved stability, and my client started recommending me to others!

Answered By ServerGuru42 On

Have you considered migrating the database to SQL? It generally offers much better stability than Access. You could start with generating a report to identify what can't be converted—who knows, maybe you’ll get lucky!

DatabaseDude22 -

Definitely a wise first step! You'll want to see what's feasible for conversion before jumping in.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.