Verdict
Submitted 5/15/2026, 9:48:24 AM · Completed 5/15/2026, 9:50:06 AM
Small business running SQL Server 2016 on EverRun (EOL July 13, 2026). Need to upgrade software ASAP. Planning a hardware upgrade later. Looking for advice on the best path forward.
Show original source text →
Strengths
- - Clear phased upgrade plan addressing immediate SQL Server 2016 EOL concerns
- - Understanding of licensing nuances, including downgrade rights
- - Recognition of the need to move off EverRun due to its costs and potential instability
- - Pragmatic approach to on-premise modernization given ERP constraints
Weaknesses
- - High costs associated with proposed HPE hardware for Phase 2
- - Potential for incompatibility issues with EverRun during the upgrade process
- - System crashes every 2-3 weeks indicate underlying stability issues that may not be fully addressed by the upgrade plan
- - Overreliance on specific hardware vendors may limit cost-saving opportunities
Best angle
Refine the upgrade plan by exploring cost-effective hardware alternatives and prioritizing the migration to a Windows Failover Cluster to enhance system stability and reduce long-term costs.
Panel verdicts
Viability
meta/llama-4-maverick-17b-128e-instruct
“The immediate focus should be on successfully executing Phase 1 within the given constraints, ensuring a stable upgrade to Windows Server 2022 and SQL Server 2022 on the existing EverRun infrastructure.”
The proposed two-phase upgrade plan is feasible for a solo or 2-person team within the given 4-12 week timeframe for v1, focusing on Phase 1. The in-place upgrade of Windows Server and SQL Server on existing EverRun infrastructure is relatively straightforward, leveraging Microsoft's downgrade rights to install 2022 versions. The main challenge lies in ensuring compatibility and a smooth upgrade process, particularly with EverRun's limitations and the current system's stability issues. The team should be cautious of potential gotchas with EverRun during the upgrade. Phase 2, involving hardware upgrades and migration to a Windows Failover Cluster, is more complex and likely to require more time and resources, potentially beyond the initial 4-12 week scope. The high cost quoted by HPE for the Gen12 servers and NVMe drives may be negotiable, and exploring third-party storage options could be beneficial. The decision to stick with on-premise ERP due to Macola/Synergy's design is reasonable. Licensing appears to be correctly understood for the most part.
Competition
nvidia/nemotron-3-nano-omni-30b-a3b-reasoning
“A specialized migration service for EverRun - bound manufacturers using Macola ERP can carve out a defensible niche, but its durability hinges on sustained expertise and adaptability to Microsoft's evolving platform.”
The idea targets a narrow niche: small manufacturers using EverRun virtualization and Macola ERP that must upgrade SQL Server 2016 before its July 2026 EOL. Existing competition includes generic Microsoft partners that offer standard in - place upgrades, third - party migration tool vendors, and broader ERP consulting firms. A dedicated service that combines license optimization, hardware sizing, EverRun replacement planning, and hands - on migration support for this specific stack is not widely offered, giving the entrant a potential differentiator. However, the market is small, the value proposition relies on expertise that can be replicated, and Microsoft's roadmap and licensing changes could erode the niche over time. Durability will depend on the ability to stay current with SQL Server releases, maintain relationships with Macola vendors, and continuously demonstrate cost - saving benefits over DIY approaches. While the concept shows a clear pain point and a plausible differentiated service, the competitive moat is modest, leading to a moderate defensibility rating.
Risk
nvidia/llama-3.3-nemotron-super-49b-v1
“Incompatible, costly legacy infrastructure (EverRun) coupled with potentially misjudged high hardware costs for the future phase threatens the viability of the upgrade plan.”
The proposed upgrade plan is fraught with technical, financial, and strategic risks that could lead to failure within 6-12 months. **1. EverRun Compatibility and Crash Risks**: The reliance on EverRun 7.9.3, which already consumes 12-15% of CPU overhead and costs $2,400/yr, poses a significant risk. Upgrading to Windows Server 2022 and SQL Server 2022 under EverRun may not resolve the recurring service crashes (every 2-3 weeks), potentially leading to downtime and compliance issues post-SQL Server 2016 EOL. **2. Exorbitant Hardware Costs for Phase 2**: The quoted $134K for HPE ML350 Gen12 servers is excessively high for a 20-user environment, indicating either a miscalculation or over-specification. This could lead to budget overrun or stalled Phase 2, leaving the system partially upgraded and vulnerable. **3. Cloud Misalignment and ERP Limitations**: The dismissal of cloud migration due to ERP design, without exploring potential cloud adaptations or newer ERP versions, might trap the business in outdated, costly on-premise solutions, limiting scalability and increasing long-term costs.
Market
qwen/qwen3-next-80b-a3b-instruct
“Small businesses with legacy ERP on EOL systems don't need cloud or shiny new hardware - they need a low-risk, budget-conscious path off unsupported fault-tolerant platforms like EverRun, and this company has the plan - they just need validation and cost-optimization guidance.”
This is a high-priority, time-sensitive upgrade for a small but mission-critical business: a 20-user wholesale distributor running an aging, unsupported ERP (Macola/Synergy) on EOL software with fault-tolerant infrastructure (EverRun) that's costly and increasingly unstable. The urgency is real - SQL Server 2016 EOL is in <2 months, and compliance/insurance risks are non-negotiable. The business has a clear budget ($17K for Phase 1), understands licensing nuances (downgrade rights), and is actively planning a phased migration - signs of a disciplined, pragmatic operator. The audience is small but highly specific: small-to-midsize businesses running legacy ERP on outdated Windows/SQL stacks with fault-tolerant virtualization. This niche is underserved; most consultants push cloud or full rebuilds, but this company needs a pragmatic, low-risk path that preserves uptime while transitioning off EverRun. The $134K HPE quote is inflated - enterprise NVMe pricing is often 3-5x retail; third-party drives (Samsung/Intel) are widely used in ProLiant servers without warranty issues if properly documented. The real unmet need isn't just upgrading software - it's finding a vendor-agnostic, cost-efficient path off EverRun without ERP downtime. The company's plan is sound: Phase 1 (in-place upgrade to Server 2022 + SQL 2022) is low-risk and budget-appropriate. Phase 2 should target a 2-node WSFC with refurbished Gen12 hardware and third-party NVMe - likely under $50K. Cloud isn't viable for Macola, so on-prem modernization is the only realistic path. This is a $100K+ problem with a $20K solution waiting to be executed.
Monetization
mistralai/mistral-medium-3.5-128b
“Phase 1 is pragmatic, but Phase 2's hardware costs can be halved with third-party drives and right-sized servers, while ditching EverRun for WSFC.”
The business has a clear, time-sensitive need (SQL Server 2016 EOL) and a phased plan with concrete pricing ($8,919 for Phase 1, $134K for Phase 2). The unit economics are reasonable for a 20-user ERP environment, but the Phase 2 hardware quote is inflated. HPE's NVMe pricing ($15K/drive) is egregious - third-party enterprise SSDs (e.g., Samsung PM9A3) would cut costs by 60-70% without meaningful risk. The licensing strategy (downgrade rights, 20 CALs) is sound, but the $2,400/yr EverRun support fee is a sunk cost that could be eliminated sooner by migrating to Windows Failover Cluster (WSFC), which is more modern and likely more stable. Cloud (Azure at $22K/yr) is overpriced for this workload; on-prem with WSFC on mid-tier hardware (e.g., $40-50K for 2 nodes) is more cost-effective. The in-place upgrade path is risky - clean VM migration is safer. Key gaps: No mention of backup/disaster recovery (critical for ERP), and the crashes may stem from EverRun or aging hardware, not SQL Server.
Synthesized by meta/llama-3.3-70b-instruct · 22.8s