SSMS 17.18 on Windows 11: SQL Files Open Failure

Understanding the File Association Conflict

Windows 11 manages which application opens specific file types through a centralized registry of associations. When you install various database tools, code editors, or even Microsoft Office components, they may claim ownership of the .sql extension. If another program takes precedence, double-clicking a script will either open it in the wrong editor or display an error stating that no suitable application is found.

This issue is particularly common after major Windows updates or when upgrading SSMS versions. The installer might not correctly register its handler, leaving the system with a broken link. Users often notice this symptom when trying to execute quick queries or debug stored procedures directly from their project folders.

Verifying the Current Default App

Before making changes, confirm which application is currently assigned to .sql files. Right-click any SQL file in your directory and select Properties. Look at the Opens with section near the top. If it does not list SQL Server Management Studio, the association is incorrect. Note that simply changing the app here sometimes fails if the system cache is stale, so a deeper reset is often required.

Resetting File Associations via Settings

The most reliable method to fix persistent association issues in Windows 11 is using the dedicated Settings interface rather than right-click menus. This approach clears cached preferences and forces the OS to re-evaluate available handlers.

1. Navigate to Settings > Apps > Default apps.
2. Use the search bar within this panel and type .sql.
3. If an entry appears, click on it to view the current default application.
4. Select Reset if the option is available, or proceed to manually assign SSMS.

If the search returns no results or the reset button is greyed out, you may need to clear the file type associations cache. This involves restarting the Explorer.exe process or rebooting the machine to ensure the registry keys are fully released before reassignment.

Manually Assigning SSMS as the Default Handler

When automatic detection fails, manual assignment ensures that SSMS 17.18 becomes the primary viewer for your scripts. This step guarantees that future double-clicks will launch the correct instance of the management studio.

• In the Default apps section under Choose default apps by file type, locate .sql.
• If it shows Choose a default, click the icon to browse installed programs.
• Scroll through the list and select SQL Server Management Studio.
• If SSMS is not listed, choose Look for another app on this PC.
• Navigate to the installation directory, typically C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Shell, and select Ssms.exe.

After selection, Windows should immediately update the behavior. Test this by double-clicking a known good SQL file. It should open in SSMS with the query window ready for execution. If it still fails, check if there are multiple versions of SSMS installed, as version conflicts can cause the wrong executable to be registered.

Alternative: Using Command Line Arguments

If the graphical interface continues to misbehave, you can verify the association by attempting to open a file via the command line. Open Command Prompt or PowerShell and run the following command, replacing the path with your actual file location:

"C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Shell\Ssms.exe" "C:\Path\To\Your\File.sql"

If this command launches SSMS correctly with the file loaded, the problem is strictly isolated to the Windows shell integration. In such cases, repairing the SSMS installation via the Control Panel > Programs and Features menu can often rebuild the missing registry entries responsible for drag-and-drop and double-click functionality.

Checking for Interfering Software

Some third-party tools, such as Notepad++, Visual Studio Code, or specialized database clients, aggressively lock file associations. If you recently installed such software, consider uninstalling it temporarily to see if the association reverts to SSMS automatically. You can also check the Default apps settings for these competitors and explicitly remove their claim on .sql files.

Additionally, group policy settings in enterprise environments may enforce specific file handlers. If you are on a corporate network, contact your IT administrator to verify that no policies are overriding user-level preferences for database file types. For home users, running SSMS as Administrator once can sometimes force a permission-based refresh of the association registry keys.

Frequently Asked Questions

Why does my SQL file open in Notepad instead of SSMS?

This happens because Windows defaults to plain text editors for unknown or unregistered file types. Notepad is often the fallback when the system cannot find a registered handler for .sql. You must explicitly set SSMS as the default in the Default Apps settings to override this behavior.

Can I associate all SQL-related extensions at once?

Yes, you can repeat the manual assignment process for .sqlproj, .mdf, and .ldf files if needed. However, only .sql requires direct editing in SSMS; others are typically data files managed by different tools. Focus on .sql first to resolve immediate workflow interruptions.

What if SSMS is not listed in the Default Apps menu?

If SSMS does not appear in the list, it means Windows has not indexed the executable properly. Use the "Look for another app on this PC" option to manually browse to the Ssms.exe file in the Program Files directory. This bypasses the auto-detection mechanism and registers the specific binary.

Does resetting file associations delete my SQL scripts?

No, changing the default application only affects how the operating system launches the file. Your data remains intact on the disk. The change is purely a pointer in the registry that tells Windows which program to start when you interact with the file icon.

How do I prevent other apps from stealing the SQL file association?

To maintain control, avoid installing multiple heavy IDEs unless necessary. If you use VS Code, configure it to handle .sql only when you explicitly open it via the file picker. Regularly review the Default Apps settings after major software installations to ensure SSMS retains its priority status.