Microsoft Excel 365 Is Not a Database
But you can make it function like one.
Excel is a spreadsheet application, not a database management system. Microsoft Access and SQL Server provide capabilities that Excel does not, including enforced data constraints, transactions, and controls for concurrent updates.
But that doesn’t mean every business process needs a traditional database. With the right design, Excel 365 can support structured records, connected data, forms, and reporting in a single application.
Start with Excel Tables
Excel Tables provide structured records with named columns and consistent references. Instead of repeating information across worksheets, data can be organized into separate Tables with identifiers that allow records to be matched and combined.
Good database design still matters. Excel does not automatically enforce primary keys or referential integrity, so those requirements must be addressed in the application.
Power Query at the Center
Power Query connects to Excel Tables, files, databases, and other sources. It cleans, combines, and transforms records through repeatable steps written in M code. Merges and appends allow developers to work with data in ways familiar to database programmers.
Power Query is primarily a tool for retrieving and transforming data. It does not, by itself, provide database transactions or write-back controls.
Relationships, Analysis, and Reporting
When a solution needs relationships across multiple Tables, the Excel Data Model and Power Pivot can support them without loading all the records onto worksheets. DAX measures, Pivot Tables, and charts then provide analysis and reporting.
Not every application needs the Data Model. A solution using Excel Tables, Power Query, and a few well-designed forms may be all that is required.
Forms and Automation
Worksheets can serve as data-entry and review forms. VBA can handle user actions, record updates, and worksheet events, while Power Query prepares the data used by those forms and reports.
Record preservation, duplicate prevention, and updates must be designed deliberately. Excel does not provide these database safeguards automatically.
A Real Access Application Rebuilt in Excel
We replaced a Microsoft Access business application we originally developed more than a decade ago with a new Excel 365 application for the same client.
The Excel application manages flow meter records, approvals, testing, and reports using a central Excel Table, connected Power Query queries, worksheet forms, and VBA.
It does not use the Data Model because the application does not need it. The tools were selected to fit the requirements, not the other way around.
Our Excel Databases article demonstrates how the application works.
When Excel Is Not the Right Choice
Access, SQL Server, or another database platform is generally a better choice when an application requires reliable simultaneous updates, strict data integrity, complex permissions, audit trails, or transactional recovery.
Sometimes the best design is to keep the records in a database and use Excel for Power Query, analysis, and reporting. Excel and databases can work together.
For more on evaluating these options, see Database Replacement Solutions for Business.
Excel Beyond the CELL
Modern Excel development goes beyond individual cells and formulas. Excel Tables, Power Query, the Data Model when needed, and automation work together to create complete business solutions.
This is the approach behind Excel Beyond the CELL.
FLUID Excel Solutions for Business.
Connect. Transform. Automate. Analyze. Deliver.























































Great article and very true.
I have been developing Excel solutions in the banking & finance sector for over 20 years and have found combining an Excel front end with a relational database backend (such as SQL Sever) a formidable, flexible and versatile combination. Your point on Excel file size is pertinent.
I’ve migrated 130 megabyte spreadsheets which took 45 minutes to calculate; to SQL Server where the results calculated in seconds with Excel retained as a flexible, dynamic reporting interface direct to the database
Thank you Marcus for the comment.
Yes, we too have done that, that is some powerful stuff right there. I built my career workign in SQL Server with Access, then Excel. SQL Server with an Access front-end works very well.
Access works very well.
But if you have smaller needs, less money, or no access to those applications, using Microsoft Excel 365 w/ Power Query will allow you to get the same results, but inside Excel.
So if you have access to Access and SQL Server, use them, if you do not, try this. Or for small needs, try this.
It works.