37

I'm DBA with a new server box running Windows Server 2008 Enterprise SP1 with SQL Server 2008 and SQL Server Management Studio.

In my previous box when working in Visual Studio with database solution with lot of .sql files I used to double-click on the .sql files and they were opened in the same SSMS instance (if any already opened). However (even when having exactly the same installation in the new box) I'm now getting a new SSMS instance when double clicking in each sql file. Its really painful one .sql - one SSMS instance so I started my research about that.

What I've tried till now:

1) Right click on the .sql file > "Open With" option > "Add" option > "Program Name: C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" and "Friendly Name: SQL" > "Ok" > "Set as Default". Does NOT work. Still having one sql - one ssms instance.

2) Perfomed Run > regedit > and modify the value data of HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\Command and replace /dde with "%1". DOES NOT WORK

3) Right click on the .sql file > "Open With" option > "Add" option > "Programe Name: explorer.exe" and "Friendly Name: Explorer" > "Ok" > "Set as default". Does NOT work. When double-clicking on the .sql files Notepad comes with scripts content.

4) Some pages like this

http://social.msdn.microsoft.com/Forums/en/sqltools/thread/ac2f39c5-66e5-495c-b7a6-47e743853baf

asks to change file association but when opening Windows Explorer > Tools > Folder Options ... I found there is no "File Type" tab. How annoying!

Can someone help me on that? My patient it's really running out.

Thanks in advance

Improve this question
7
  • When you say instance you really mean connection, right? You want each SQL script to share a single connection? Commented Aug 19, 2011 at 14:51
  • 8
    @Yuck, no he means when he goes to Windows Explorer and double-clicks a .sql file, it opens a new instance of Management Studio. Commented Aug 19, 2011 at 14:53
  • Aaron, you're right. This is going to kill me soon!. Any clue?! Commented Aug 19, 2011 at 15:05
  • If you're running Win7 the file associations you are looking for are in "Control Panel\Programs\Default Programs" Commented Aug 19, 2011 at 15:13
  • 1
    possible duplicate of SQL Management Studio won't open scripts on double-click Commented Jul 23, 2014 at 15:29

14 Answers 14

Reset to default
24

After spending most of my working day looking for the solution I finally found it. Thanks God, I was almost running out with this issue. Hope it helps somebody else!!!.

Update: linked domain expired, so here's what it said:

Considering how integrated Microsoft tools usually are the result is frustrating when you tell Visual Studio to open SQL files using Sql Server Management Studio (SSMS). I really don't like using Visual Studio to edit T-SQL files but in the past, before I discovered this tip, each SQL file I opened would open in a new instance of SSMS. Try it:

  1. Open a solution which contains SQL files
  2. Right-click any SQL file and select “Open With…”
  3. Click “Add”
  4. Browse to "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" or if you're running x64 Windows "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe", then click “OK”
  5. Click “Set as Default” and then “OK”

Now open multiple SQL files. Each time you'll get a different instance of SSMS opened. What a pain!

NOTE: This entire article applies to SQL 2005, just replace SSMS with SQLWB.

How do you resolve this? Repeat steps 1-3 above, but at step #4 enter the following values:

  • Program Name: “explorer.exe”
  • Friendly Name: “Windows Explorer”

Repeat step #5 (set as default) above and then click OK. Now, open additional files. They should all open in the same instance of SSMS.

It would seem that Visual Studio issues a command to SSMS.exe which includes the path of the file selected in the solution explorer. It is up to SSMS to check for a new instance, which it doesn't. But when you pass the file name to explorer it gets opened up in the same instance.

QUIRK WARNING!

If SSMS is not already open, the first file you attempt to open (not first time ever, but every time you open an SQL file from Visual Studio and SSMS isn't open yet) SSMS will open, but your file will not. Click the file a 2nd time and it will open the file this time. Don't ask me to explain it it just is (and I have no idea why). Conclusion

The result when you tell Visual Studio that SSMS is the default editor makes sense, but I don't get why it would be different when you tell explorer to open it. Maybe if I were a Windows developer instead of a web developer I would know the answer. But either way, now you know. Enjoy.

Improve this answer
Sign up to request clarification or add additional context in comments.

6 Comments

I guess I did something wrong or this solution is not always working: when I set C:\Windows\explorer.exe to the default program for .sql files and then click on a sql file, it keeps starting new explorer.exe processes until Doomsday.
And somehow, the .sql extension was chucked out of the registry as well :-)
I've tried this solution, but it almost froze my machine. Windows explorer entered in a kind of look trying to open the file, and I had to hit Ctrl-Alt-Del to close it.
Note to readers: this question relates to opening SQL files FROM VISUAL STUDIO, not from windows explorer!! This confused me for some time and explains all the talk of 'open with explorer.exe' which is otherwise just weird.
Side-note: explorer approach mentioned in the wnaser works perfectly with Visual Studio 2012/SSMS 2012
|
11

I have this problem before, I found there is a simple solution -> just check if your SSMS is under "Run this program as an administrator" option (right click on the shortcut icon -> property -> Compability -> Privilege level). If yes, untick the option and try double click the sql file.

Hope this helps.

Improve this answer

4 Comments

It works, for some reason I tend to run development-related software under admin privileges, so I'm not happy with this setting. Nevertheless, if it works, one doesn't argue with it.
A quick note for users who want to have SSMS always open with Administrator privileges. Find SSMS in your start menu. Right-click>More>Open File Location. Once you see the shortcut to Microsoft SQL Server Management Studio * in Windows Explorer, Right-click>Open File Location. Then Right-click on Ssms.exe>Troubleshoot compatibility. Then click Troubleshoot program. Put a tick by The program requires additional permissions then hit Next. Now it forces you to press Test the program.... Then press Next and then Yes, save these settings for this program.
Sadly, for some reason though, this did not work for me. Using Microsoft SQL Server Management Studio 18. :(
For SQL Server Management Studio 2019, there is no "Privilege level" under Compatibility. Right Click SSMS > Properties > Advanced > Untick Run as administrator.
5

My issue with multiple SSMS instances version 19 was fixed by changing HKEY_CLASSES_ROOT.sql Default key to

enter image description here

Improve this answer

1 Comment

most visually easy option to cover. Please note that now days its SQL v19 available so just replace to ssms.sql.19.0
3

Similar issues have been reported multiple times, but they aren't addressing the issue (removed links because Microsoft erased Connect without much thought):

Did you install Visual Studio (or any Visual Studio components) after installing SQL Server?

My guess is that the Connect items will not be fixed - SQL will blame Visual Studio, Visual Studio will blame SQL, and the items will remain open...

So here is what I suggest: run a repair of SQL Server from Programs and Features and then re-apply the latest service pack of SQL Server 2008 (SP2).

Also the "File Types" interface was moved from the Tools / Folder Options interface to the Control Panel. Go into Control Panel > Default Programs > "Associate a file type or protocol with a program." However it doesn't seem to have the options here to add command-line options like "%1" or /dde.

Improve this answer

3 Comments

Also this TechNet thread has several recommendations for replacements of the File Types tab and bringing back a lot of those options that seem to have been moved to individual Open With wizards or taken away completely. Perhaps you could try one or more of these utilities and see if they have the ability to restore proper functionality: social.technet.microsoft.com/Forums/en/itprovistadesktopui/…
The first 3 Links for this answer do not work anymore.
@JohnFoll Yeah, that's what happens after 10 years.
1

Try adding these reg keys as well, but make sure you put the /dde back in:

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\ddeexec]
@="Open(\"%1\")"

For the record, here is my entire export for that section:

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open]

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\Command]
@="\"C:\\Program Files (x86)\\Microsoft SQL Server\\100\\Tools\\Binn\\VSShell\\Common7\\IDE\\ssms.exe\" /dde"

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\ddeexec]
@="Open(\"%1\")"

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\ddeexec\application]
@="sqlwb.9.0"

[HKEY_CLASSES_ROOT\sqlwb.sql.9.0\Shell\Open\ddeexec\topic]
@="system"
Improve this answer

Comments

1

Go to Tools >> Folder Options >> File Types and apply below settings. It worked for me finally!!! (after half a day search on google).

  1. Click New/Edit (on this window "Confirm open after download" should be check and "Always show extension" should be unchecked)

  2. In next window, make below entries

       - Action: Open
   - Application used to perform action : Your ssms.exe path like "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
   - Check "Use DDE" check box
   - DDE Message : Open("%1")
   - Applicajtion sqlwb.9.0
   - DDE Application Not Running: Keep it empty
   - Topic : system

    Regards, Sandeep Gaadhe

Improve this answer

Comments

1

I am using SQL Server Management Studio 2012 Express and I have made this to work by pointing "Program" to "explorer.exe"

This is how my register is set up: "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe" /dde

at

HKEY_CLASSES_ROOT\ssms.sql.11.0\Shell\Open\Command

Improve this answer

Comments

0

I've 2005 & 2008 SSMS installed so I defaulted to the 2005 instance. If I have 2008 ssms open when opening a .sql file from windows explorer it will now open in the existing 2008 ssms (and not try to open a new instance!)

Improve this answer

Comments

0

From Windows Explorer, one can drag-and-drop selected files (single or multiple) into an SSMS window.

Improve this answer

Comments

0

One thing to check is if you have multiple versions of SSMS. If you happen to be working in an older version, double clicking on a file will open the new SSM version. Or whatever the default version is for sql files.

Improve this answer

Comments

0

A quick note for users who want to have SSMS always open with Administrator privileges.

  • Find SSMS in your start menu. Right-click>More>Open File Location.
  • Once you see the shortcut to Microsoft SQL Server Management Studio * in Windows Explorer, Right-click>Open File Location.
  • Then Right-click on Ssms.exe>Troubleshoot compatibility.
  • Then click Troubleshoot program.
  • Put a tick by The program requires additional permissions then hit Next.
  • Now it forces you to press Test the program....
  • Then press Next and then Yes, save these settings for this program.

Arvo Bowen Jan 30 '20 at 15:27

This work perfectly.

Improve this answer

Comments

0

I know this is quite an old post and there are loads of different answers with possible solutions. But here's one I think is new (at least to SO).

I suddenly starting getting this behaviour (i.e. each new file would open in a new session) and couldn't figure out why. Turns out it was because in my SSMS session I had an open dialogue which had dropped into the background.

A soon as I closed the dialogue, new files started opening in my original session /facepalm

Maybe everyone knows this already but just in case it saves anyone 20 mins!

Improve this answer

Comments

0

Old question, but in my case, in the recent list of apps to open for .sql files, there were both "SQL Server Management Studio" and "SSMS 18" listed, which was causing it to open a new instance.

I selected "Choose another app", selected "SQL Server management Studio", and checked "Always use this app to open .sql files." Problem solved.

Improve this answer

Comments

0

Try this registery update:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\ssms.sql.19.0]
@="Microsoft SQL Server Query File"
[HKEY_CLASSES_ROOT\ssms.sql.19.0\DefaultIcon]
@="C:\\Program Files (x86)\\Microsoft SQL Server Management Studio 18\\Common7\\IDE\\ssms.exe,-10000"
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell]
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell\Open]
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell\Open\Command]
@="\"C:\\Program Files (x86)\\Microsoft SQL Server Management Studio 19\\Common7\\IDE\\ssms.exe\" /dde"
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell\Open\DdeExec]
@="Open(\"%1\")"
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell\Open\DdeExec\Application]
@="ssms.19.0"
[HKEY_CLASSES_ROOT\ssms.sql.19.0\Shell\Open\DdeExec\Topic]
@="system"

Doesn't work with newer versions of SSMS as it is integrated in the visual studio suite

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.