SQL Server "PRIMARY filegroup is full" — Why Does It Fail to Grow?
Diagnosing SQL Server Error 1105 PRIMARY filegroup full, inspecting sys.database_files, fixed MB vs percentage autogrowth, MAXSIZE vs OS disk capacity, and dedicated user filegroups.
Operational Verification & Reliability Metadata
The error string is a symptom, not the root cause. Do not restart the server blindly. Run the diagnostic queries below to pinpoint the actual failure mode.
▸Symptoms
Could not allocate space for object 'dbo.Siparis' in database 'app'
because the 'PRIMARY' filegroup is full.▸Resolution Patterns
- 1Set Fixed-MB Autogrowth:
ALTER DATABASE app MODIFY FILE
(NAME = app_data, SIZE = 20GB, FILEGROWTH = 512MB, MAXSIZE = 200GB);- 1Add Secondary Data File:
ALTER DATABASE app ADD FILE
(NAME = app_data2, FILENAME = 'D:\Data\app_data2.ndf', SIZE = 10GB, FILEGROWTH = 512MB)
TO FILEGROUP [PRIMARY];- •Related Error: SQL Server Msg 9002 Transaction Log Full
- •Companion Guide (Oracle): Oracle ORA-01653 Tablespace Full
- •Engine Hub: SQL Server Production Hub
Other Database Error Triage Playbooks
Other battle-tested diagnostic guides for high-severity database errors.
SQL Server Error 18456: Root Cause by State Code Matrix
In Error 18456, the State code reveals the actual root cause. Specific fixes for State 5, 8, 11, 18, 38, and 40, with ERRORLOG extraction scripts.
SQL Server Error 1205 Deadlock: Graph Extraction and Prevention
Extracting the deadlock graph from the system_health Extended Events ring buffer, understanding victim election, and architectural resolution.
SQL Server Pool Timeout: Connection Pool Exhaustion Fix
Difference between connection pool timeout and query command timeout, detecting connection leaks, and .NET DbContext architectural fixes.