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

by

Why This Error Happens

Error 1819 occurs when SQL Server attempts to generate a default name for the transaction log file (.ldf) by concatenating the database name with a timestamp or GUID-like suffix, and the resulting string exceeds the maximum allowed file name length (typically 260 characters including the full path). This is most commonly triggered when creating a database with an extremely long name, restoring a database with WITH MOVE to a deeply nested folder path, or scripting automated database creation where naming conventions append excessive metadata. Windows Server 2025 and Windows 11 still enforce legacy MAX_PATH limitations by default unless long path support is explicitly enabled.

Step-by-Step Resolution Guide

Step 1: Shorten the Database Name or Target Path

  • Review the CREATE DATABASE or RESTORE DATABASE statement for excessively long database names.
  • Reduce nested folder depth in the data/log file destination, e.g., move from C:\SQLData\Projects\2025\Archive\CustomerRecords\Logs\ to a shorter path like D:\SQLLogs\.
  • Rerun the command with the shortened identifiers.

Step 2: Explicitly Specify Logical and Physical File Names

  • Avoid relying on SQL Server’s auto-generated default naming logic.
  • Use explicit file definitions in your script:
CREATE DATABASE MyDB
ON PRIMARY (NAME = MyDB_Data, FILENAME = 'D:\SQLData\MyDB.mdf')
LOG ON (NAME = MyDB_Log, FILENAME = 'D:\SQLLogs\MyDB_log.ldf');
  • Ensure the FILENAME path stays well under 260 characters.

Step 3: Enable Long Path Support in Windows (If Applicable)

  • Open the Local Group Policy Editor (gpedit.msc) on Windows Server 2025 or Windows 11.
  • Navigate to Computer Configuration > Administrative Templates > System > Filesystem.
  • Enable the policy “Enable Win32 long paths.”
  • Restart the SQL Server service for changes to take effect: net stop MSSQLSERVER && net start MSSQLSERVER.

Step 4: Validate SQL Server Instance Default Directories

  • Check default data and log directory settings in SQL Server Management Studio (SSMS) under Server Properties > Database Settings.
  • Ensure these default paths are short and valid, such as D:\SQLData\ and D:\SQLLogs\.
  • Update any registry-level or configuration-level paths that may be unnecessarily long.

Alternative or Verification Steps

  • After applying fixes, re-run the original CREATE DATABASE or RESTORE DATABASE command and confirm it completes without Error 1819.
  • As an alternative, use sp_helpdb or query sys.master_files to verify the generated file paths are valid and under the character limit before executing any database creation scripts in production.