0

Synopsis

This is not a new problem and there are several solutions floating around on Internet.

Problem

When you double click on a .sql file, a new instance of SSMS is opened. I did not have this problem until new SQL Server Management Studio (SSMS 17.9.1) was installed.

What I tried

  • This page lists several solutions suggesting registry changes and file associations, and reinstalling SSMS. None worked.
  • This one has almost the same as the previous link. (SO is so much better than those forums.)
  • Registry changes are shown here with excellent screenshots. I added "%1" but that did not make any difference.
  • The suggestion mentioned on SO did not work either.
  • On DBA, it is mostly talking about raised permissions, which is not the case with my situation.

Workarounds

Yes, I know about these workarounds:

  • Ctrl + O
  • Drag .sql files to SSMS

I am not looking for workarounds.

My environment

Even with the new SSMS 17.9.1 (build: 14.0.17289.0), I am still pointing to SQL Server 2016 (13.0.5233.0). Previously, I was using SSMS June 2016 (build: 13.0.15000.23) with the same SQL Server (13.0.5233.0).

Because of permission, I am not running any application as administrator.

SQL Server versions are listed here.

SQL Server Management Studio versions are listed here.

Farhan
  • 2,535
  • 4
  • 32
  • 54
  • Are you running SSMS as administrator? If so, are you also running Explorer as administrator (or wherever you are double-clicking)? – tgolisch Apr 11 '19 at 14:23
  • @tgolisch No, nothing is being run as administrator. – Farhan Apr 11 '19 at 14:24
  • 1
    I think this really belongs on SuperUser. This issue really is not related to SSMS specifically. VTC – UnhandledExcepSean Apr 11 '19 at 14:35
  • FWIW, I have no such problem with my copy of SSMS 17.9.1 on W10, so this is not a universal and unfixable issue. (SQL Server versions are irrelevant; this is strictly an OS/application issue.) – Jeroen Mostert Apr 11 '19 at 14:44

0 Answers0