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

by

Why This Error Happens

This error occurs because SQL Server 2025 prevents a DROP DATABASE operation when one or more file snapshots (used for features like database cloning or point-in-time recovery snapshots) are still associated with the database. The underlying VDI (Virtual Device Interface) or sparse file snapshot references lock the database files at the filesystem level, meaning SQL Server cannot safely remove the physical files until those dependent snapshots are cleaned up. This typically happens after using database cloning features (DBCC CLONEDATABASE) or third-party backup tools that leverage Volume Shadow Copy Service (VSS) snapshots.

Step-by-Step Resolution Guide

Step 1: Identify Existing File Snapshots

  • Open SQL Server Management Studio (SSMS) and connect to the instance via a New Query window.
  • Run the following query to list active snapshots tied to the database:
  SELECT * FROM sys.database_file_snapshots;
  • Note the database_name and snapshot_id values returned, as you will need these to target the cleanup.

Step 2: Delete the File Snapshots Manually

  • Execute the sp_delete_file_snapshot stored procedure to remove the orphaned snapshot metadata and clear the lock:
  EXEC sp_delete_file_snapshot N'<Full_Path_To_Snapshot_File>';
  • If the exact file path is unknown, cross-reference the path column from the sys.database_file_snapshots query in Step 1.
  • Repeat this command for every snapshot entry associated with the problematic database.

Step 3: Verify Filesystem Lock Release

  • Navigate to the default data directory (typically C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA) using File Explorer or PowerShell.
  • Check if the .vhdx or sparse file snapshot artifacts have been removed from the disk following the EXEC command.
  • If files remain locked, restart the SQL Server (MSSQLSERVER) service via the Services console (services.msc) on Windows Server 2025 to release any lingering file handles.

Step 4: Retry the Drop Command

  • Return to your query window and attempt the deletion again:
  DROP DATABASE [YourDatabaseName];
  • Confirm that Error 3755 no longer appears in the Messages tab of SSMS.

Alternative or Verification Steps

  • Verification: Run SELECT name FROM sys.databases WHERE name = 'YourDatabaseName'; to confirm the database no longer exists in the instance catalog.
  • Alternative Fix: If snapshots cannot be deleted due to active application connections, use ALTER DATABASE [YourDatabaseName] SET OFFLINE WITH ROLLBACK IMMEDIATE; followed by a database Detach (right-click DB > Tasks > Detach) rather than a hard drop, then manually delete the physical .mdf, .ldf, and snapshot files from the Windows Server 2025 file system.