For many JD Edwards customers, Microsoft SQL Server remains a core database platform alongside Oracle Database. With its wide adoption, SQL Server customers have long requested stronger capabilities around high availability (HA) and disaster recovery (DR). At INFOCUS 2025, Pradip Pandey and the JD Edwards product team unveiled significant enhancements designed to meet these needs—bringing SQL Server support closer to the robust continuity options already available with Oracle Database.
Why SQL Server Enhancements Matter for JD Edwards
Business continuity is critical for enterprise systems. Customers running JD Edwards on SQL Server want seamless failover, minimal downtime, and the ability to leverage the latest Microsoft SQL Server features. These enhancements respond directly to customer requests, including those from Quest’s Tech SIG community, ensuring JD Edwards remains resilient in today’s demanding IT environments.
Key Enhancements in the Upcoming Release
- Support for SQL Server Clustering
The most significant development is support for two types of SQL Server clustering:
- Always On Failover Cluster Instances (FCI):
Provides HA at the SQL Server instance level. In case of node failure, the entire SQL Server instance fails over to another node with minimal downtime. This option is simpler to manage, suitable for single data center setups, and included with SQL Server Standard Edition. - Always On Availability Groups (AG):
Offers database-level HA and DR, replicating user databases across multiple instances. Secondary replicas can handle read-only workloads, improving scalability and load distribution. While more complex to configure, AGs are ideal for geographically distributed deployments and require SQL Server Enterprise Edition.
By supporting both FCI and AG, JD Edwards gives customers flexibility to choose the best-fit strategy for their environment.
- Planned Failover for Seamless Maintenance
Maintenance windows and patching often create risk for downtime. With these enhancements, JD Edwards environments can perform graceful planned failovers—minimizing disruption while updates are applied. EnterpriseOne servers automatically reconnect to the new SQL Server node within minutes, preserving business operations during scheduled outages.
- Read-Only Routing for Load Balancing
For Availability Groups, JD Edwards now supports read-only routing. This feature directs read-intent queries to secondary replicas, balancing workloads and improving overall system performance. With configuration through ODBC and JDBC connection settings, enterprises can reduce pressure on primary replicas while ensuring high throughput.
Technical Considerations and Best Practices
Failover Behavior
- Planned Failovers: Smoothly redirect workloads, allowing administrators to patch systems without extended downtime.
- Unplanned Failures: In-flight transactions are not preserved and must be restarted manually. While SQL Server clustering minimizes outage impact, Oracle noted that unplanned outage handling is not yet automated for SQL Server environments.
Configuration Recommendations
- Validate Windows Server Failover Clustering (WSFC) prerequisites.
- Optimize JD Edwards Enterprise Server and HTML Server settings, including connection pools and timeouts, to ensure fast reconnection after failover.
- Use synchronous commit and automatic failover modes for minimal data loss in Availability Groups.
- Conduct full backups before rolling upgrades to avoid unexpected issues during patch cycles.
Performance Testing Results
Oracle’s internal testing showed promising outcomes. Failovers completed within a few minutes, with EnterpriseOne applications reconnecting automatically. Batch and interactive workloads performed within acceptable variance (+/-5%) before and after failover. This gives customers confidence that system resiliency can be achieved without sacrificing performance.
Looking Ahead
These SQL Server database enhancements represent a major step forward in JD Edwards’ HA and DR capabilities. By extending clustering support, enabling read-only routing, and aligning with Microsoft’s latest database technologies, Oracle is equipping customers with the tools they need to maintain uptime, improve scalability, and reduce risk.
As organizations modernize their JD Edwards environments, these options provide the flexibility to align database architecture with business continuity requirements—whether within a single data center or across multiple geographies.
Want more?
Explore more content and resources to help you get the most from your JD Edwards investment:
- Be sure to check out the INFOCUS 2025 Event Hub (coming soon) for presentation slides – available exclusively to Quest members.
- Explore the JD Edwards Orchestrator Strategic Content Center for more Quest-exclusive resources.
- Visit the Quest Learn Library for blogs, how-to demos, and on-demand sessions.
- Connect with peers in one of our Quest JD Edwards Community User Groups to swap stories, ask questions, and share tips with other users facing the same challenges.
Not a Quest member yet? Join today and tap into the ultimate Oracle customer network.