I know there is already a thread on this but it is old. When ever I double click on a .sql file it opens a new instance of SSMS. This is annoying and not the behavior that I'd expect. When the new instance opens the file will be there BUT I get an error message, "There was a problem sending the command to the program."

I'm running SQL Server 2012 SP1 on Windows 7. Does anybody have a modern fix for this issue?

• Edited by falcon00 Wednesday, May 21, 2014 4:47 PM

Hello,

Please try the below procedure, but first backup the registry.

Run regedit and go to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ssms.sql.11.0\Shell\Open\Command

Edit the default value to add "%1" to the end.

The value should now look like the following:

"c:\Program Files\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe" /dde "%1"

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Naomi NEditor Wednesday, May 21, 2014 5:19 PM
• Unproposed as answer by falcon00 Wednesday, May 21, 2014 7:15 PM

No dice. Do I need to reboot my machine?

You may try to re-boot.

BTW, I was trying to find a way to fix that File Association directly in Windows 7 and it seems we need to use a free utility for that

http://www.thewindowsclub.com/change-file-associations-windows

BTW, for me it works fine (doesn't open a new SSMS instance).

OK. I'm in the middle of something. Let me try rebooting in a bit.

No dice.

Can you verify if that registry entry stick? Also, did you check the link I posted? I think you should be able to fix the file associations this way, but it seems to require a freeware utility. I haven't downloaded it, so I haven't verified. You may want to try it.

The registry entry did stick after the reboot. I downloaded that utility and it wasn't helpful. The file is associated properly. The icon shows it as a sql file and all the windows tools show ssms as the default program. It just refuses to open in an existing instance and without throwing an error.

What is the cmd Shell command to open .sql files? Without that utility I was not able to find out my own command, but I think last parameter should be '% 1' meaning open in the same instance.

"C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe" /dde "%1"

that's what it looks like. The only difference from above is that it's (x86) instead of just Program Files.

Hi falcon,

According to your description and error message, there is an feedback to Microsoft such this similar issue. For more information, see: http://www.beta.microsoft.com/SQLServer/feedback/details/705728/ssms-doenst-launch-when-dclick-on-sql-file.

However, it was closed as they could not reproduce.  I would recommend to submit this feedback again to the Microsoft Connect at this link https://connect.microsoft.com/SQLServer/Feedback, and descript more detail  about for your scenario to help us to reproduce the issue. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft Connect.

Thanks,

Sofiya Li

BTW, in my case the command is just

"c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe" /dde

E.g. no % 1 at the end. It still works OK for me and opens the sql file in the existing instance of SSMS.

BTW, Sofiya, I am getting the exact same issue often when I don't have SQL Server opened and try to double click on the .sql file the first time.

Wondering if the existing issue can be re-opened instead of creating a ne

"c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe" /dde is what mine looked like originally. After a day of googling I'm convinced there is no solution to this issue because nobody understands the cause. There is probably something obscure wrong with my machine and the only fix is to reimage the HD. :(

Would it be possible to open a case with MS?

I will this weekend.

• Proposed as answer by Naomi NEditor Thursday, May 22, 2014 3:29 PM
• Marked as answer by Sofiya LiMicrosoft contingent staff, Moderator Wednesday, May 28, 2014 2:52 AM
• Unmarked as answer by Naomi NEditor 14 hours 13 minutes ago

Did you open a case with MS, I know this is an old thread but did you find any resolution I am working with SS 2014.

No I never did find any resolution.

• Edited by falcon00 15 hours 15 minutes ago