SQL Server secondary data file recovery

A missing NDF can remove part of a database even when the MDF and log still open.

NDF files are secondary data files that can hold complete tables, indexes, partitions, LOB data, or allocation maps. They are not optional simply because the primary MDF still exists.

Start a recovery case Call 682-325-7712

Understand the symptom

SQL Server allocates pages across files according to filegroup configuration and growth history.

WHY

What is happening

Database metadata records each file ID and logical name. Objects may span MDF and NDF files, while partitioned objects can live primarily in a secondary filegroup. Recovery therefore needs the complete file map, log sequence, and backup chain rather than treating an NDF as an auxiliary cache.

What you may see

Symptoms that change the recovery path.

Operating system error opening NDF

The path, volume, permission, or physical file is unavailable.

Database remains suspect

Startup recovery cannot read pages allocated to the missing file.

Only some tables fail

Affected objects or partitions may reside in the missing filegroup.

NDF has I/O or checksum errors

The file exists but important pages cannot be read reliably.

Protect the source

Actions that can make the situation worse.

Removing the file abandons allocated pages

SQL metadata may be made consistent by sacrificing objects stored there.

Empty-file operations require readable pages

DBCC SHRINKFILE cannot safely evacuate data from a missing or corrupt file.

New file creation overwrites the old path

Reusing the same storage can destroy recoverable NDF sectors.

Do this now

Safe steps before evaluation.

Stop SQL and application activity

Prevent retries, restores over the database, detach, attach, and automatic repair.

Preserve all database files

Copy MDF, every NDF, LDF, FILESTREAM data, backups, and transaction-log backups.

Document the file map

Save sys.database_files output, filegroup layout, object placement, paths, sizes, and error logs.

Protect the missing file's storage

Image the volume or disk before formatting, chkdsk, replacement, or reuse.

NEPFOSYS process

How a data-first evaluation proceeds.

Filegroup mapping

NEPFOSYS identifies file IDs, object allocation, backup coverage, and the missing NDF's role.

Storage and file acquisition

Readable NDF regions and the complete database set are preserved.

Targeted database recovery

Priority objects are reconstructed and validated with the available log and backup context.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Is an NDF less important than the MDF?

No. It can hold unique table, index, partition, and LOB pages required by the database.

Can I create a blank NDF with the same name?

No. A new file has no relationship to the original page allocations and can overwrite recoverable storage.

Can backups restore only the missing file?

SQL Server supports file and filegroup restore in suitable recovery models, but success depends on a valid backup and log chain.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case