For CFOs, controllers, and IT leaders at businesses using Sage 100 with Microsoft SQL Server, the way future SQL Server licensing is purchased and managed has changed. On July 31, 2026, the agreement that allowed Sage to distribute SQL Server Runtime licenses ended as Microsoft retired the ISV Royalty program.
Existing Runtime licenses remain valid, so you do not need to replace a working SQL Server environment. The change affects how you store and access your ERP, and how much you will have to pay to do so: Sage can no longer sell new Runtime licenses or add users to existing ones. When your business needs additional SQL licensing, it must be purchased through a Microsoft reseller.
What Changed
The former Microsoft ISV Royalty program allowed Sage and other software providers to offer SQL Server Runtime licenses for use with their products. Runtime licenses were product-restricted: a SQL Server license purchased with Sage 100 could be used for Sage 100, but not for a separate SQL-based application.
Effective August 1, 2026, Sage can no longer sell new SQL Runtime licenses, add Client Access Licenses (CALs) to existing Runtime licenses, or renew SQL Runtime maintenance under the former program.
What Has Not Changed
Existing Sage 100 SQL Runtime licenses do not stop working because of this change. If your business purchased or renewed an eligible Runtime license on or before July 31, 2026, you can continue using your current SQL Server environment indefinitely. There is no required migration or reason to replace a stable installation solely because Sage can no longer sell or renew Runtime licenses.
Upgrade rights are different. Sage’s notice allows eligible customers to move to newer SQL Server versions distributed by Sage during their current agreement term. Before planning an upgrade, confirm your agreement end date and the SQL Server version available under that agreement. After the term ends, confirm which upgrade options remain available before committing to a version, budget, or project schedule, especially when planning a broader Sage 100 2026 upgrade.
What Future SQL Licensing Looks Like
The change matters when your business needs additional SQL Server licensing. That could mean adding employees who need Sage 100 access, opening a new location, or expanding remote access. A deployment change, such as a server replacement or move to a hosted Sage 100 environment, is also a good time to review your SQL licensing needs. Sage can no longer sell new Runtime licenses or add users to an existing Runtime license.
For future SQL Server needs, licenses must be purchased through a Microsoft reseller or channel partner. Depending on the reseller and your needs, SQL may be available as Runtime or Full Use. Sage is working with Microsoft distributor Pax8 to help partners source Full Use SQL licenses through the Microsoft Cloud Solution Provider program. Those licenses are assigned to named users rather than shared concurrently, so confirm exactly who needs access before purchasing.
Full Use licenses have a higher initial price than Runtime licenses, but the Sage notice describes them as more cost-effective for most customers over time. They are not limited to Sage 100, can be used with other eligible SQL-based applications, and do not require annual renewal. The appropriate licensing decision depends on your user count, other SQL Server applications, and expected growth.
What CFOs and Controllers Should Review
Before hiring, expansion, or upgrade decisions become urgent, your finance and IT teams should conduct a short SQL licensing review. The review should document your current licensing, identify where additional licensing may be needed, and establish who will make future purchasing decisions. It should answer six questions:
- What SQL Runtime licenses and CALs does your business currently own? When does your agreement term end, and what upgrade entitlement remains through that date?
- How many Sage 100 users in your business require SQL access today, and is each user properly covered?
- Are there expected hires, acquisitions, new locations, or access changes that could increase the number of users who need access?
- Which version of SQL Server are you using, and what is your expected Sage 100 and SQL Server upgrade path, including 64-bit readiness? Coordinate that assessment with your broader Sage 100 2026 64-bit upgrade checklist.
- Does your business operate other SQL-based applications that could make Full Use licensing more practical?
- Who owns your future SQL license purchasing, recordkeeping, and approval decisions—finance, IT, a Sage partner, or a Microsoft reseller?
Budgeting and Ownership Need Clearer Attention
Under the previous model, your business could handle a Runtime license or additional CAL as part of a Sage-related purchase. Under the new model, future SQL licensing requires a separate Microsoft procurement decision, which may change your budget owner, approval path, and timing of the purchase.
You may first see the change when your Sage renewal invoice no longer includes a SQL Runtime charge. That does not mean SQL Server is now free. Sage cannot renew the legacy Runtime maintenance arrangement, and future user additions or new SQL licenses require a separate Microsoft purchase.
A simple documented process can prevent future confusion. Document where your current license records reside. Have IT confirm your user count and technical requirements. Your business should also identify which advisor or reseller will be involved when a new SQL license, user, or upgrade is needed.
Plan Before the Next Change
This program change removes a familiar route for future licensing. By documenting your current environment and assigning ownership, you will be better prepared when user growth, an upgrade, or an infrastructure change requires action.
Contact SWK Technologies to review your current Sage 100 SQL licensing position, identify future requirements, and plan your next licensing or upgrade decision.