Skip to content

Issue with compressed drive – SQL Server database

ERROR:
SQL Server database is coming online and below error message is written to SQL Server error log:-

2013-03-26 17:17:44.18 spid53 Error: 5118, Severity: 16, State: 1.
2013-03-26 17:17:44.18 spid53 The file "E:\mssql\Data\mssql\Data\myelvisdata.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2013-03-26 17:17:44.26 spid53 Error: 5118, Severity: 16, State: 1.
2013-03-26 17:17:44.26 spid53 The file "E:\mssql\Data\mssql\Data\myelvislog.ldf" is compressed but does not 
reside in a read-only database or filegroup. The file must be decompressed.
2013-03-26 17:17:44.29 spid53 Error: 928, Severity: 20, State: 1.
2013-03-26 17:17:44.29 spid53 During upgrade, database raised exception 945, severity 14, state 2, address 01597E14. Use the exception number to determine the cause.

CAUSE:
In NTFS file system you may face issues with SQL Server databases if drive where database files are stored is compressed. When a drive containing database files were compressed then the database may become unavailable / will not come come online and will write above error message in SQL Server error log.

You may not face this issue if the read only database files are stored in compressed drive.

RESOLUTION:
In order to resolve and/or avoid this issue you have to uncompress the drives where database files are stored. Once uncompressed try to bring database online (if instance is up and troublesome database was not master or tempDB) or try to restart this SQL Server id issue was with master or tempDB.