How to fix Error 1825 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 1825 – Filegroups and Collations Cannot Be Specified for Database Snapshots

Why This Error Happens

This error occurs because database snapshots in SQL Server are designed to be exact, read-only, point-in-time copies of the source database, and therefore inherit all structural properties—including filegroup mappings and collation settings—directly from the source. SQL Server 2025 blocks any CREATE DATABASE ... AS SNAPSHOT OF statement that explicitly attempts to redefine a COLLATE clause or assign files to a new or different FILEGROUP, since snapshots do not support independent schema structures. This is typically triggered by script templates copied from standard CREATE DATABASE syntax that were not stripped of these incompatible clauses before execution against a snapshot definition.

Step-by-Step Resolution Guide

Step 1: Review and Strip the T-SQL Syntax

  • Open the script that is throwing Error 1825 in SQL Server Management Studio (SSMS) or Azure Data Studio.
  • Locate the CREATE DATABASE [SnapshotName] AS SNAPSHOT OF [SourceDB] command.
  • Manually delete any COLLATE <collation_name> arguments found in the file definition list.
  • Remove any FILEGROUP keyword declarations; snapshot files must be listed as a flat set of NAME and FILENAME pairs only, without group association.

Step 2: Correct the Sparse File Path Mapping

  • Ensure every file in the source database (including secondary data files) is mapped to a corresponding sparse file in the snapshot command.
  • Use the correct file extension convention, such as D:\SQLData\Snapshots\SourceDB_data.ss, to avoid confusion with standard .mdf/.ndf files.
  • Verify the destination directory exists and that the SQL Server service account has write permissions to that specific path in Windows Server 2025.

Step 3: Validate Source Database Compatibility

  • Check that the source database is not currently in SIMPLE recovery mode, as this does not block snapshots but confirm the file structure hasn’t changed since the last schema modification.
  • Run sp_helpfile against the source database to get the exact logical names required for the snapshot script, ensuring they match character-for-character (case-sensitive).
  • Re-execute the cleaned CREATE DATABASE statement without the collation or filegroup arguments.

Step 4: Restart the SQL Server Service (If Cached Plan Persists)

  • If the error persists due to a cached execution plan or metadata lock, open Services.msc on the Windows Server 2025 host.
  • Locate SQL Server (MSSQLSERVER) or the specific named instance.
  • Right-click and select Restart to clear any transient metadata locks before re-attempting the snapshot creation.

Alternative or Verification Steps

  • Verify the fix by querying sys.databases and checking that the source_database_id column is populated for the new snapshot, confirming it was created successfully without errors.
  • If the issue persists, use the SSMS GUI Wizard (Right-click Databases > New Database > uncheck “Specify Filegroups” if available) instead of raw T-SQL, as the GUI automatically omits invalid snapshot parameters.