Fix it now
Error 1827’s published text is that the resulting cumulative database size would exceed your licensed limit per database. On Express that limit is 10 GB up to SQL Server 2022 and 50 GB on SQL Server 2025. No setting, trace flag or extra data file changes it. Free space to buy time, or change edition to remove it.
SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS Version;
EXEC sp_spaceused;
SELECT name, type_desc, size * 8 / 1024 AS SizeMB, max_size FROM sys.database_files;
- Check the edition and version together. The limit you are up against depends on both, and people quote the 10 GB figure at servers where it is not the number.
- Compare what
sp_spaceusedreports as allocated against the ceiling for your release. Close to it with the volume half empty is the licensed limit, not the disk. - Free space that is genuinely free: drop indexes nothing reads, then archive or delete cold rows in bounded batches.
- If the data is needed and growing, run setup, Maintenance, Edition Upgrade with a licensed key. The cap lifts and no data moves.
Error 1105 is the neighbouring message and its published text now covers both cases: a filegroup full through lack of storage space, or through database files reaching the maximum allowed size. Read which one you actually got before deciding it is a licensing problem.
If the write that failed now succeeds, you are done. If not, the next section explains what the limit covers and which of the two errors you are looking at.
Why it happens
Express is the free edition, and the free edition is bounded. Microsoft publishes those bounds in the editions tables as scale limits, and the one people meet first is the maximum relational database size: 10 GB per database on SQL Server 2019 and 2022, and 50 GB per database on SQL Server 2025. It is per database, not per instance, which is why one database can be stuck while others on the same instance are fine.
1827’s published text is specific about when it fires: CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit per database. So it is the statement that changes a database’s size that gets refused. The message you are more likely to see from an ordinary insert is 1105, whose published text reads that the filegroup is full “due to lack of storage space or database files reaching the maximum allowed size”. Both point at the same wall from different sides.
Adding a second data file does not help. The limit is on the cumulative size, so five gigabytes plus five gigabytes is still ten. Splitting the data across two databases does work, because each database has its own allowance, and it costs nothing – but you pay elsewhere, in cross-database queries, in backups that have to stay consistent with one another, and in referential integrity you now enforce in application code.
One thing worth being careful about: Microsoft publishes the ceiling as a maximum relational database size per database and does not publish an itemised list of what is and is not counted towards it. Plenty of advice on this subject asserts that logs, or FILESTREAM data, or something else is excluded. Measure with sp_spaceused and sys.database_files rather than trusting an exclusion nobody can point at.
The database has genuinely grown past what the edition allows
You have this one if sp_spaceused shows allocated space close to the ceiling for your release, the edition is Express, and the volume has plenty of room.
- Find the largest consumers before deciding anything, with the per-object allocation query in the reference section below rather than by guessing which table is the problem.
- Decide honestly whether that data is live. If it is, no amount of housekeeping holds the line for long.
- If it is live and growing, plan the edition upgrade rather than repeating this exercise every quarter.
Space is being wasted inside the file
You have this one if sp_spaceused shows a large unused figure, and reserved space far exceeds the data actually stored.
- Look for indexes nothing reads, using
sys.dm_db_index_usage_stats. It resets when the service restarts, so judge it over a full business cycle rather than a quiet afternoon. - Drop those indexes and archive historical rows into a second database on the same instance.
- Shrink the data file once with
DBCC SHRINKFILEto return the freed space, then rebuild the indexes that shrinking fragmented.
Shrinking is not a routine operation. It fragments indexes heavily and the space it releases is reclaimed by normal growth, so do it once after a genuine deletion, never on a schedule.
Documents, images or audit history are sitting in the live database
You have this one if A handful of tables holding binary data or audit rows account for most of the size.
- Move that data to a second Express database on the same instance. Each database has its own allowance.
- Or keep the files outside the database and store only a path in the row.
- Consider page compression on the largest remaining tables. Microsoft states that from SQL Server 2016 Service Pack 1 the edition-specific features except transparent data encryption are available across editions, and data compression is one of them.
Splitting across databases is free and it works, but it is a way of buying time rather than a design. Cross-database queries, referential integrity and backup consistency all become your problem.
It is 1105 and the volume really is full
You have this one if 1105 alone, and the drive holding the data file has no free space.
- Check the volume before anything else. 1105’s published text covers ordinary out-of-space as well as the licensed ceiling.
- Free disk, or grow the file if autogrowth was capped by a MAXSIZE setting rather than by the edition.
- Read
max_sizeinsys.database_files: a file with an explicit maximum will refuse to grow long before any edition limit is reached.
Full reference
What Express is actually bounded by
| Scale limit | SQL Server 2019 and 2022 Express | SQL Server 2025 Express |
|---|---|---|
| Maximum relational database size | 10 GB | 50 GB |
| Maximum memory for buffer pool per instance | 1,410 MB | 1,410 MB |
| Maximum compute capacity for a single instance | Lesser of 1 socket or 4 cores | Lesser of 1 socket or 4 cores |
| Columnstore segment cache per instance | 352 MB | 352 MB |
| Memory-optimised data size per database | 352 MB | 352 MB |
Those limits bite together. A database that has grown to the size ceiling is almost always also short of buffer pool, because 1,410 MB does not go far against ten or fifty gigabytes of data. That is why an edition change often resolves two complaints at once, and why adding RAM to an Express machine changes nothing at all.
Working out where the space went
| What you see | What it means |
|---|---|
| Inserts fail while the drive has plenty of free space | The licensed cap, not the disk |
| Index rebuilds fail but small inserts still work | The rebuild needs contiguous room the cap will not allow |
| 1105 and the volume is full | Ordinary out of space. Free disk or grow the file |
1105 and max_size in sys.database_files is set |
A per-file maximum somebody configured, not the edition |
| One database stuck, others on the same instance fine | The limit is per database |
| 1827 from a CREATE DATABASE or ALTER DATABASE | The statement itself was refused for exceeding the licensed size |
Measuring rather than assuming
EXEC sp_spaceused;
SELECT name, type_desc,
size * 8 / 1024 AS SizeMB,
max_size
FROM sys.database_files;
SELECT OBJECT_NAME(p.object_id) AS ObjectName,
SUM(a.total_pages) * 8 / 1024 AS TotalMB
FROM sys.partitions AS p
JOIN sys.allocation_units AS a ON a.container_id = p.hobt_id
GROUP BY p.object_id
ORDER BY TotalMB DESC;
What actually removes the limit
- An edition upgrade. Run setup from media for the same version, Maintenance, Edition Upgrade, and supply the key. Your databases stay where they are and the outage is the service restart.
- Nothing else. There is no trace flag, registry value, startup parameter or configuration option that raises it, and anything on the internet offering to patch the binaries is not something to run on a server holding your data.
- Note the direction of travel: there is no in-place downgrade either, so an instance moved up cannot be moved back without an uninstall and reinstall.
After the upgrade
Set max server memory (MB) deliberately once the edition has changed, because the buffer pool ceiling has just lifted from 1,410 MB to whatever the new edition allows and the engine will happily take everything the machine has. Leave the operating system real headroom, apply the value, and watch free physical memory over the following day rather than guessing repeatedly. If the instance was Express, remember that SQL Server Agent does not exist there, and Microsoft’s edition-upgrade documentation notes that the Agent service has to be enabled and its service account configured after the upgrade.
Buying time honestly
| Tactic | What it costs you |
|---|---|
| Dropping unused indexes | Nothing, if you judged usage over a full business cycle |
| Archiving cold rows to a second database | Cross-database queries and backup consistency become your problem |
| Page compression on large tables | CPU on every read and write of those pages |
| Moving binary content out of the database | Backup and restore no longer carry the files with the rows |
| Shrinking after a deletion | Heavy index fragmentation, so rebuild afterwards |
| A second Express instance | Another 1,410 MB buffer pool ceiling and another four-core cap to work within |
When a licence is the actual fix
There is no free route past the licensed size limit. It is part of what Express is, and every tactic above postpones it rather than removing it. SQL Server 2025 Standard (2-core pack) has no practical per-database size limit, and it lifts the Express memory and processor ceilings at the same time, which is usually what the same server needs next. The change is an in-place edition upgrade: no data movement, no reattaching, an outage the length of a service restart. Core licences are sold in two-core packs, so the quantity follows the cores the instance runs on rather than the size of the database. Where the user population is small and countable, Server plus CAL is worth comparing. Send Arco the core count and we will tell you which shape costs less for your situation.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1827 |
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed the licensed limit per database | Microsoft Learn |
1105 |
Space could not be allocated because the filegroup is full, either through lack of storage space or through database files reaching the maximum allowed size | Microsoft Learn |
Confirm the fix worked
- The insert, update or index rebuild that previously failed now completes.
SELECT name, size * 8 / 1024 AS SizeMB, max_size FROM sys.database_files;shows the data file able to grow past its previous ceiling.- If you upgraded,
SELECT SERVERPROPERTY('Edition');returns the paid edition. EXEC sp_spaceused;shows headroom your monitoring can alert on before you get here again.- If you upgraded from Express,
max server memory (MB)has been set deliberately rather than left at its default maximum.
Questions people ask about this
Is the Express limit 10 GB or 50 GB?
Both, depending on the release. Microsoft’s editions tables give Express a maximum relational database size of 10 GB on SQL Server 2019 and 2022, and 50 GB on SQL Server 2025. Check SERVERPROPERTY(‘ProductVersion’) before quoting a figure at anyone.
Is there a trace flag or registry key that removes the limit?
No. It is a scale limit of the edition, not a configurable option, and there is no supported way to raise it. The supported answer is a different edition.
Does the transaction log count towards the limit?
Microsoft publishes the figure as a maximum relational database size per database and does not publish a breakdown of what counts. Rather than rely on an exclusion nobody documents, measure with sp_spaceused and sys.database_files. If your log file is what is consuming the disk, that is a recovery model and log backup issue and it is fixed separately.
Can I split the database and stay on Express?
Technically yes, because each database has its own allowance, and it costs nothing. The price is paid in queries that span databases, backups that must be kept consistent with each other, and referential integrity you now enforce in application code.
What does moving off Express cost?
It depends on the edition and the cores the instance runs on, or on your user count if Server plus CAL suits you better. Core licences come in two-core packs, so the count matters. Send us the core count and we will quote against it.
