
There is an application in your organization that nobody wants to touch. It was built in Visual FoxPro, probably by someone who retired or moved on, it holds data the business cannot lose, and it still runs every day. Microsoft stopped supporting Visual FoxPro years ago, so every year the application stays put it gets harder to fix, harder to secure and harder to staff. Many organizations feel trapped: the system works, the data is critical, and nobody can say what a replacement would take. This guide is for the people who have to answer that question, and it starts with the good news that moving off Visual FoxPro is a solved problem.
Short answer
Microsoft’s lifecycle page lists Visual FoxPro 9.0 mainstream support ending in January 2010 and extended support ending on January 13, 2015, and Microsoft announced in 2007 that there would be no Visual FoxPro 10. Since the end date there are no new security updates, no non-security updates and no assisted support. Moving the data to SQL Server is usually the straightforward part. Replacing the application is the real project, because the business rules, screens and reports live in the Visual FoxPro code. There is no SSMA for FoxPro (Microsoft’s migration assistant supports Access, Db2, MySQL, Oracle and SAP ASE). Visual FoxPro includes its own SQL Server Upsizing Wizard, which is a helpful starting point for the data and not a migration plan. The way out is to separate the data, the rules and the screens, move each deliberately, and test the results against the old system.
Series: this is the final part, part 9, of our series on moving legacy databases to SQL Server. Part 1 covers Microsoft Access, part 2 covers Excel, part 3 covers Oracle, part 4 covers SAS, part 5 covers Sybase / SAP ASE, part 6 covers PostgreSQL, part 7 covers MySQL, part 8 covers Db2, and the complete guide explains why, what it takes and how it is tested.
At a glance
- Where things stand: Visual FoxPro 9.0 reached end of support on January 13, 2015. Its last service pack was released in 2007, and Microsoft has said there will be no newer version.
- Why organizations are trapped: business rules buried in code, developers who have retired, missing documentation, forms and reports that people rely on, and no clear estimate for a replacement.
- The tool gap: no SSMA for FoxPro. The Upsizing Wizard inside Visual FoxPro can create a SQL Server database from a Visual FoxPro database, but it has limits, and large tables can take hours.
- Where the risk is: deleted records that are only marked, string comparisons that match a shorter value, blank dates, numeric precision, and rules that live in code instead of the database.
- How we start: a free, no-obligation discovery call, then a written assessment and plan you approve before any work begins. No setup fees and no minimum contract.
Why are so many organizations trapped on Visual FoxPro?
- The application is the documentation. Business rules sit inside forms, programs and reports, and the original developers are gone. Nobody can list what the system does, so nobody can estimate a replacement.
- The data is irreplaceable. Customer history, financial records, archives and research collections have to remain accessible and correct. The risk of losing them outweighs the cost of waiting.
- People rely on the screens. Staff know the screens and reports by heart. A migration that moves only the data leaves them dependent on the old interface.
- Skills are scarce. Fewer developers know the language every year, so each change request is slower and riskier than the last.
- Moving looks like a rewrite. Visual FoxPro mixes the language, the data engine and the screens, so replacing it can look like rebuilding everything at once. That is why a staged plan matters.
- The business keeps changing. New systems, new reporting needs and new security expectations all assume a database server, not files on a share.
What are the risks of staying on Visual FoxPro?
Microsoft’s lifecycle notice for products that reached end of support says there are no new security updates, no non-security updates, no free or paid assisted support options and no online technical content updates. In practice, the risks are:
- No security updates or vendor help for the development environment or its runtime.
- Operating system uncertainty. Community reports on Microsoft’s own Q&A site are mixed on Windows 11: some people run Visual FoxPro 9 SP2 on it without trouble and others report missing runtime errors. There is no Microsoft position to rely on, and a new PC or server image can break an application overnight.
- Hard limits. A Visual FoxPro table file cannot exceed 2 GB, a record holds at most 255 fields, character fields top out at 254 characters, and a field name in a free table is limited to 10 characters. Growth eventually runs into those limits.
- Integration friction. Modern reporting, APIs, single sign-on and cloud services are hard to connect to a file-based desktop application.
- Key-person and skills risk. Support depends on one or two people, or on outside developers who are also aging out.
- Audit and compliance questions about unsupported software holding important records.
None of this means the application is about to fail. It means the risk grows slowly and then arrives all at once, usually on a Friday afternoon. A plan made now is cheaper than a rescue later.
What kind of Visual FoxPro system do you have?
| Type of system | What it usually looks like | Usual approach |
|---|---|---|
| A data archive | Tables that must stay searchable, with little or no daily data entry. | Load the data into SQL Server and add a simple search and report interface. |
| A desktop application with moderate logic | A handful of forms and reports that staff use every day, with rules in the code and in the database container. | Move the data to SQL Server, rebuild the application as a web application, and run both side by side until results match. |
| A large business application | Many forms, reports, scheduled jobs and integrations, often with third-party components. | Phase the work by area. Move data first, then replace modules in a planned order. |
When is it reasonable to wait, or to move only part of it?
An honest assessment sometimes recommends waiting on part of the system. Waiting is reasonable when the application is stable, the data is small and backed up, access is restricted, the risk of a failure is low, and a rewrite would cost more than the application is worth. It is not reasonable to wait with no plan. The minimum is a documented inventory, tested backups, a copy of the application and its runtime files, and a decision date. Moving the data to SQL Server first can also reduce risk while the application stays in place.
Where can Visual FoxPro and SQL Server give different results?
These differences turn a “simple conversion” into a project. None of them stops a load, and each one can change a result, which is why we list them first in an assessment. The behaviors below come from Microsoft’s archived Visual FoxPro documentation and Microsoft’s SQL Server documentation, and each should be tested against your own data.
| Area | In Visual FoxPro | In SQL Server, and what to do |
|---|---|---|
| Deleted records | DELETE marks a record for deletion but does not remove it. SET DELETED defaults to OFF, so many commands still see marked records, and PACK removes them physically. | A SQL Server row is either there or gone. Decide whether marked records are migrated, archived or dropped, and whether the application ever treated them as live. |
| String comparison | With SET EXACT OFF (the default), an = comparison only needs to match until the end of the right-hand value. The == operator requires an exact match, and SET EXACT does not apply inside Visual FoxPro SQL commands. | SQL Server compares whole values. Lookups that relied on partial matching return different rows, so find where the code depends on the setting and rewrite those searches. |
| Blank dates | An empty date is a normal value that works in comparisons and arithmetic. | SQL Server has no blank date. Use NULL or a placeholder date, chosen column by column, and check any code that tests for an empty date. |
| Numbers and types | Numeric and float fields hold up to 20 digits, integers range up to 2,147,483,647, and character fields hold up to 254 characters. | Microsoft’s Upsizing Wizard maps Numeric to float by default, which is rarely right for money or quantities. Choose decimal precision deliberately, and use varchar(max), nvarchar(max) and varbinary(max) instead of the text and image types the wizard lists, which Microsoft says will be removed. |
| Rules and integrity | Validation rules and referential integrity live in the database container and are enforced by the engine. Much of the real logic is in forms and programs. | The Upsizing Wizard turns validation rules into stored procedures called from triggers, and relationships into triggers or constraints, but it does not upsize existing Visual FoxPro triggers. Rules written in forms must be rebuilt in the new application or database. |
| Language style | A procedural xBase language that often walks records one at a time. | T-SQL and application code work with sets of rows. Record-by-record loops are rewritten as queries, which is where performance and behavior can change. |
| Capacity limits | A table file is limited to 2 GB, with up to 255 fields per record. | SQL Server removes these limits. Express edition holds up to 50 GB per database in SQL Server 2025, and Standard and Enterprise hold far more. |

What replaces what in SQL Server and a modern application?
| In Visual FoxPro | Usually becomes | Watch for |
|---|---|---|
| DBF tables, memo (FPT) and index (CDX) files | SQL Server tables and indexes | Memo and general fields become varchar(max) or varbinary(max), and Visual FoxPro tags become SQL Server indexes. |
| Database container rules, defaults and relationships | Constraints, defaults, triggers and stored procedures | Rules that were enforced silently by the engine now need to be written and tested. |
| Forms (SCX) and menus | Web pages in a new application | Navigation habits and keyboard shortcuts that users depend on. |
| Reports (FRX) and labels | Reports in the web application, SQL Server Reporting tools or Power BI Report Server | Exact layouts and print formats that someone has to approve. |
| Program files (PRG) and class libraries | Stored procedures and application services | Business logic that is not written down anywhere else. |
| Visual FoxPro queries (Rushmore-optimized) | T-SQL queries with SQL Server indexes | Performance tuning is redone for the new engine. |
| COM and ActiveX components, third-party controls | Modern libraries or web services | Components that are no longer sold or maintained. |
| Desktop executable and runtime files on a file share | A browser-based application on a server | Access control, deployment and backup move from the file share to the server. |
How do you move the data from Visual FoxPro to SQL Server?
The Upsizing Wizard. Visual FoxPro includes a SQL Server Upsizing Wizard. Microsoft describes it as creating a SQL Server database that duplicates, as much as possible, the functionality of a Visual FoxPro database. It can move local data to a server, turn local tables and views into remote tables and views, and help migrate a local application to a client/server application. Microsoft’s own documentation warns that large tables may need several hours, and it does not upsize Visual FoxPro triggers. Use it to get a first copy of the data and to see what needs attention, then review the result.
Other routes. Data can also be exported to delimited files and loaded with SQL Server bulk tools or SQL Server Integration Services, or read directly through a database driver. Tools that read these files often depend on older 32-bit drivers, so the extraction method is planned early. Whatever the route, the steps are the same:
- Copy first. Work from a copy of the tables, memo files and indexes, and keep the original untouched until the new system is accepted.
- Profile the data. Count records, find deleted records, blank dates, trailing spaces, duplicate keys, orphaned child records and fields that hold more than one kind of value.
- Decide the rules. Write down how deleted records, blank dates and numeric precision are handled, and have a business owner approve them.
- Load into staging. Use explicit type mappings and exception handling, and keep source identifiers so every row can be traced.
- Reconcile. Compare record counts, totals and key relationships after every rehearsal.
- Rehearse the cutover before any production date.
What are the options for the overall design?
| Route | What happens | Best for | Trade-off |
|---|---|---|---|
| A. Archive and search | Load the history into SQL Server and add a simple search and reporting interface. | Systems that are mostly historical records. | New data entry still needs a home. |
| B. Data first, application later | Move the data to SQL Server and keep the Visual FoxPro screens for a while by connecting them to the server, then replace modules in stages. | Large applications where a rewrite cannot happen at once. | A stepping stone, not a destination. The unsupported front end remains for now. |
| C. New web application on SQL Server | Migrate the data and build a replacement application for entry, lookup and reporting, then retire Visual FoxPro. | Systems staff use every day. | The largest effort, with the largest payoff. Needs side-by-side validation. |
| D. Phased by area | Replace one function or department at a time, with integration between old and new during the transition. | Large estates with many modules. | Both systems run for a while, so interfaces must be managed. |
Our approach follows seven steps:
- Discover: inventory the tables, forms, reports, programs, scheduled tasks, integrations and users. Interview the people who use the system every day, because they know things the code does not say.
- Assess: classify each form, report and program as used daily, used occasionally, or unused. Capture the business rules and the definitions that must not change.
- Architect: choose the route, the SQL Server edition or Azure SQL target, the application stack, security and the reporting approach.
- Plan: a phased plan with a cost model, the order of work, test scenarios, the cutover window and rollback criteria.
- Implement: migrate the data, build the replacement application, and rebuild the reports and scheduled work.
- Validate: reconcile data, compare outputs between old and new, and let business users test real work in the new system.
- Support: train users, document the system, monitor it, and retire Visual FoxPro and its runtime files.
What usually breaks when you move from Visual FoxPro to SQL Server?
Most problems are known and fixable, which is why the assessment comes first. These show up most often:
- Deleted records that were never really gone, and reports that relied on SET DELETED.
- Lookups that depended on partial string matches.
- Blank dates that become NULLs or placeholders and change report results.
- Numeric rounding when fields were mapped to float.
- Business rules that lived in forms and were never written down.
- Reports whose exact layout someone expects on paper.
- Relationships that the old engine enforced silently and the data does not actually satisfy.
- Record-by-record logic that runs slowly or differently as set-based SQL.
- Components and controls that are no longer available.
- Users’ habits: shortcuts, screen flow and the way they search.
What does it look like when a Visual FoxPro collection moves to SQL Server?
Here is an anonymized example. A global entertainment company kept part of its artist recording-session history in a Visual FoxPro database and desktop application. The application held millions of records that had to remain accessible while the business kept adding new information. The modernization needed to preserve that historical collection and give employees a practical replacement for the desktop application, because moving the records alone would have left users dependent on the old interface for everyday work. The company engaged Everconnect to migrate the Visual FoxPro data to SQL Server and build a completely new web front end covering new record entry, easy lookup and reporting.

| Requirement | Modernization response |
|---|---|
| Millions of historical records needed to move out of Visual FoxPro. | Migrated the recording-session records into SQL Server, making the historical collection available through the replacement application. |
| Employees needed to continue entering new session information. | Built web-based entry forms so new records could be created within the modernized system. |
| Historical information needed to be easy to find. | Created a searchable web interface for locating and reviewing recording-session records. |
| Users needed reporting alongside everyday record access. | Built reporting into the new application so employees could retrieve information and produce reports through the same interface. |
| Replacing the database alone would leave the legacy desktop workflow in place. | Delivered a complete replacement front end rather than requiring users to continue working through Visual FoxPro. |
Migrating the historical collection. The data migration was central to the project. Millions of recording-session records represented a substantial historical resource, and their usefulness depended on remaining understandable and accessible after the move. The work focused on carrying the existing information into a SQL Server structure that could support both historical lookup and continued data entry. Record relationships, and the connection between stored information and its presentation in the application, were important parts of that transition. The target served two purposes: preserving access to the historical collection and supporting the records the business would create next.
Building a completely new web application. Everconnect built a new web front end around the three activities the company needed:
- New record entry. Employees enter recording-session information through web forms backed by SQL Server. This established a continuing workflow in the replacement system rather than treating the migration as an archive-only exercise.
- Easy lookup. A browser-based search lets users find and review the migrated records, without navigating the Visual FoxPro application.
- Integrated reporting. Reporting is part of the replacement application, connecting routine record lookup with the ability to organize and present information for business use.
Together, these functions replaced the legacy presentation layer and made SQL Server the foundation for ongoing use of the collection.
What the company gained.
- Millions of records migrated. The recording-session data moved from Visual FoxPro to SQL Server.
- A complete replacement interface. A newly built web application provides entry, lookup and reporting.
- Historical and new information in one environment. Employees work with the migrated collection while continuing to add records.
- Continued value from historical data. Pairing the database migration with an accessible front end preserved the usefulness of the records.
Why it matters. Legacy applications often contain information whose value extends far beyond the technology originally used to store it. For this global entertainment company, the project brought millions of recording-session records into SQL Server and provided a new way to use them. The combination of historical migration and a complete web application supported both preservation and ongoing business activity.
How do you work out the cost, and whether it is worth it?
A Visual FoxPro replacement is usually a custom project, so estimates start from what the system does, not from its size on disk. We do not quote a savings percentage, and we do not promise one. A useful comparison is a model built from your own numbers:
- Cost of staying: the people or contractors who keep the application running, the cost of an outage, the time lost to workarounds, and the risk exposure of unsupported software holding important records.
- Cost of moving: assessment, data migration, the replacement application, reports, testing, training and cutover.
- Cost of SQL Server: the edition that fits the workload and licensing method, or Azure SQL, plus hosting, backup and monitoring. SQL Server Express is free and limited to 50 GB per database in SQL Server 2025, which suits some archives.
- Cost of phasing: running both systems for a period, and the interface work between them.
Almost all Everconnect consulting work over the last 24 months has been billed between $125 and $145 per hour. There are no setup fees and no minimum contract length. We estimate after the free, no-obligation discovery call and an assessment. See our pricing page for the full picture.
Which SQL Server should you move to?
Pick a target that is still supported. SQL Server 2016 ended support on July 14, 2026, so a project starting now should look at SQL Server 2022 or 2025, or Azure SQL. Microsoft lists SQL Server 2025 Standard at up to 4 sockets or 32 cores and 256 GB of buffer pool memory, with SQL Server Agent included, while Enterprise edition lifts those limits. Express edition is free and does not include SQL Server Agent. Because SQL Server can run on Windows and Linux, and in Azure, a web application on SQL Server is easier to host, back up and secure than a set of files on a share.
Where should you start this week?
- Find every Visual FoxPro application: servers, desktops, scheduled tasks and the people who rely on each one.
- Copy the data files, memo files, indexes, source code and runtime files to a safe location, and test that a restore works.
- List the forms, reports and scheduled jobs, and mark which ones are used every day.
- Ask the daily users what they would be unable to do without the system.
- Check the size of the largest tables against the 2 GB file limit.
- Record where the application runs: which Windows version, which server, and who can change it.
- Decide the goal: preserve the data, replace the application, add integration, or all three.
Migrating is also how you get AI-ready data
A migration from Visual FoxPro is the best time to fix the data, not just move it. FoxPro tables and memo fields often hold free text and codes that were never standardized. While every table is mapped to SQL Server, duplicates can be matched, codes standardized and columns described, which is the same work that makes data usable for AI. In the RSM Middle Market AI Survey 2026, data quality and availability was the most-cited obstacle to deploying AI (34 percent), and 28 percent named legacy systems integration. Those figures describe the survey respondents, not Everconnect clients. See AI for Your Data for how we start with a data readiness review.
Get help
Everconnect Data Systems provides migrations from Visual FoxPro to SQL Server and builds replacement web applications. Book a free, no-obligation discovery call to talk through your Visual FoxPro system, or see our database migration services, SQL Server consulting services and managed database services. Once the data is in SQL Server, the SQL Server Health Check ($499 per server) can review the new server’s configuration, security and backups.
Frequently asked questions
No. Microsoft’s lifecycle page lists Visual FoxPro 9.0 mainstream support ending in January 2010 and extended support ending on January 13, 2015. The last service pack, SP2, was released in 2007, and Microsoft announced in 2007 that there would be no Visual FoxPro 10. After the end of support there are no new security updates, no non-security updates and no assisted support from Microsoft.
Because the application works, the data is critical and replacing it looks risky. Business rules are buried in code and forms, the original developers have left, documentation is missing, and users depend on the screens and reports. Without a clear estimate, the replacement keeps getting postponed. A structured assessment is what turns the unknown into a plan.
No security updates or vendor support, uncertainty about newer operating systems, hard limits such as a 2 GB table file and 255 fields per record, difficulty integrating with modern reporting and cloud services, and dependence on a few people who still know the language. The risk grows slowly, so a plan made now is cheaper than a rescue later.
Community reports are mixed. Some people say Visual FoxPro 9 SP2 runs on Windows 11 without trouble, and others report missing runtime errors that community-built runtime installers sometimes fix. Microsoft offers no support or position, so we do not recommend planning around it. Treat any new PC, server image or operating system upgrade as a risk to the application.
Not an SSMA. Microsoft’s SQL Server Migration Assistant supports Access, Db2, MySQL, Oracle and SAP ASE, not FoxPro. Visual FoxPro includes its own SQL Server Upsizing Wizard, which creates a SQL Server database from a Visual FoxPro database, and it is a useful starting point for the data, not a complete migration.
It creates a SQL Server database that duplicates, as much as possible, the functionality of a Visual FoxPro database, moves data, and can turn local tables and views into remote ones. Microsoft’s documentation says large tables can take hours, validation rules become stored procedures called from triggers, and existing Visual FoxPro triggers are not upsized. It maps Numeric to float by default, so the types need review.
Copy the tables, memo files and indexes first, profile the data for deleted records, blank dates, trailing spaces and broken relationships, decide and document the rules, load into staging tables with explicit type mappings, reconcile counts and totals, and rehearse the cutover. The load can use the Upsizing Wizard, exported delimited files with SQL Server bulk tools or Integration Services, or a direct driver connection.
Common choices are Character to char or varchar, Integer to int, Date and DateTime to date or datetime2, Logical to bit, Currency to money or decimal, Memo to varchar(max) and General to varbinary(max). Numeric fields should be mapped to decimal with a chosen precision rather than float. Microsoft’s older wizard lists text and image types, which Microsoft says will be removed, so modern equivalents are used.
In Visual FoxPro, DELETE only marks a record for deletion, the record stays in the file until PACK is run, and SET DELETED is OFF by default. A migration must decide whether marked records are loaded, archived or dropped, and whether any report or process treated them as live. We confirm the rule with the business owner.
Visual FoxPro treats an empty date as a normal value. SQL Server has no blank date, so each column gets a rule, either NULL or a placeholder date, and any code that tests for an empty date is rewritten. The choice affects report results, so it is documented and approved before the first load.
With SET EXACT OFF, which is the default, a Visual FoxPro = comparison only needs to match until the end of the right-hand value, so a longer value can match a shorter one. SQL Server compares whole values. Searches and lookups that relied on partial matching return different rows, so we find them and rewrite them on purpose.
Forms are replaced by web pages or another modern front end, reports are rebuilt in the new application or a reporting tool, and business logic in programs and forms becomes stored procedures or application code. The business rules are written down first, because they often exist only in the code, and users approve the results.
Often for a while. Moving the data first and connecting the existing screens to the server can reduce risk and give you a modern database foundation, and Microsoft’s Upsizing Wizard is built for that pattern. It is a stepping stone, because the unsupported front end remains, so we plan the replacement of the screens at the same time.
Yes. In one of our projects, a global entertainment company moved millions of recording-session records from Visual FoxPro to SQL Server and gained a completely new web application for new record entry, easy lookup and reporting, so employees no longer worked through the old desktop application.
It is more common than you would think. The assessment starts from what the system does: the data, the screens and reports in use, and the people who run it every day. Where the source code is missing, the data can still move to SQL Server and the replacement is built from observed behavior, with outputs compared between the old and new systems.
It depends on the data volume and quality, how many forms, reports and jobs exist, how much undocumented logic there is, whether the application is replaced or only the data moves, and how much testing the business needs. A written assessment turns those counts into an estimate. We do not quote a duration before we have seen the system.
Almost all Everconnect consulting work over the last 24 months has been billed between $125 and $145 per hour, so 40 hours is about $5,000 to $5,800 and 80 hours about $10,000 to $11,600. A migration with a replacement application is a larger engagement than that, and we estimate after the free, no-obligation discovery call and an assessment. There are no setup fees and no minimum contract. See our pricing page.
By reconciliation and side-by-side testing. Compare record counts, totals and key relationships after every data load, run the same searches and reports in both systems and investigate every difference, and let daily users try real work in the new system before Visual FoxPro is retired.
Not automatically. A migration moves the data; whether it is ready for AI depends on whether duplicates, inconsistent codes and undocumented columns are fixed along the way. FoxPro tables and memo fields often hold free text and codes that were never standardized. Mapping every table is a natural time to fix those. See AI for Your Data.
Related guides
- Migrating legacy databases to SQL Server: the complete guide
- Is your business running on a Microsoft Access app? What to do before it breaks
- Is your business running on Excel spreadsheets? When to move to SQL Server
- Should you migrate from Oracle to SQL Server? Costs, risks and how it works
- Should you migrate from SAS to SQL Server? Reasons, risks and how it works
- Should you migrate from Sybase (SAP ASE) to SQL Server? Reasons, risks and how it works
- Should you migrate from PostgreSQL to SQL Server? When it makes sense and when it doesn’t
- Should you migrate from MySQL to SQL Server? Reasons, risks and how it works
- Should you migrate from Db2 to SQL Server? Reasons, risks and how it works
- SQL Server migration with minimal downtime: methods compared
- How to choose a SQL Server migration consultant (and what to ask)
Updated November 2, 2026. Written by Nathan Jaskot, founder of Everconnect Data Systems, a US-based, veteran-owned database consulting firm founded in 2010. Microsoft facts were checked against Microsoft’s documentation on that date (sources below). Visual FoxPro documentation is archived and describes older versions, so test every behavior on your own system.
Sources (checked November 2, 2026)
- Microsoft Lifecycle: Microsoft Visual FoxPro 9.0
- Microsoft Lifecycle: Ending support in 2015
- Wikipedia: Visual FoxPro (release history and the 2007 announcement)
- Microsoft Q&A: Microsoft Visual FoxPro (community reports on Windows 11)
- Microsoft Learn (archive): Visual FoxPro System Capacities
- Microsoft Learn (archive): SQL Server Upsizing Wizard
- Microsoft Learn (archive): Mapping Visual FoxPro Databases to SQL Server Databases
- Microsoft Learn (archive): SET EXACT Command
- Microsoft Learn (archive): SET DELETED Command
- Microsoft Learn: Data type conversions (text, ntext and image removal note)
- Microsoft Learn: SQL Server Migration Assistant (supported sources)
- Microsoft Learn: Editions and supported features of SQL Server 2025
- Microsoft Lifecycle: Ending support in 2026
About the author. Nathan Jaskot is the founder of Everconnect Data Systems, Inc., a US-based, veteran-owned database and technology consulting company he started in 2010. Everconnect works with SQL Server, PostgreSQL, MySQL, Oracle, Azure and AWS. Learn more about Everconnect.






