SQL Server Error 1105 — Could not allocate space, filegroup is full

Could not allocate space for object 'X' in database 'Y' because the 'PRIMARY' filegroup is full.

Unlike error 9002 (the transaction log), this is about a data filegroup running out of room to store new rows/index pages — it's reached its size limit or the disk itself is out of space.

Common causes

• The data file hit a configured maximum size limit
• The underlying disk drive is genuinely out of free space
• Autogrowth is disabled, or set to a fixed small increment that can't keep up with write volume
• A single filegroup holding everything on a database that has outgrown its original sizing

How to fix it

1. Check current file sizes and growth settings: SELECT name, size, max_size, growth, is_percent_growth FROM sys.database_files.
2. If the disk has room, either let autogrowth handle it or manually grow the file (ALTER DATABASE ... MODIFY FILE) rather than waiting on an emergency autogrowth event.
3. If the disk is full, free space, move the file to a larger volume, or add a second data file on a different disk.
4. Review whether old/unused data can be archived or purged to reduce the growth rate going forward.

Related

• Error 9002 — Transaction log full