SSMS 2017 v3 - files open disconnected, no connection option

Question

SSMS 2017 v3 - files open disconnected, no connection option

schleep

SSChampion

Points: 12585
More actions
December 4, 2017 at 12:43 pm

#333881

Maybe I am just missing something, but when I double-click on a .sql file, it opens connected, or at least offers a choice.
When the same file is renamed .prc, it opens disconnected, and there is no way to make a connection.
Where is the setting for this?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Thom A SSC Guru Points: 99133 More actions · Answer 1

At a guess it's because SSMS doesn't know what to do with a .prc file. SSMS is really only designed with sql and sqlplan files in mind. Google tells me that a .prc file is "... a 3D file format that can be used to embed 3D data in a PDF file." Why would you want to open 3D data in a SQL Server Administration tool?

It might seem silly, but there's an "easy" solution to this: save your SQL files as .sql files, don't give them a different extension.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

schleep SSChampion Points: 12585 More actions · Answer 2

It's worked fine for me from SQL 6.5 - 2008R2: Tools, Options, Text Editor, File Extensions

And at least though 2K8R2, you had the option to connect when the query editor window was disconnected.

Thom A SSC Guru Points: 99133 More actions · Answer 3

schleep - Tuesday, December 5, 2017 5:55 AM
It's worked fine for me from SQL 6.5 - 2008R2: Tools, Options, Text Editor, File Extensions
And at least though 2K8R2, you had the option to connect when the query editor window was disconnected.

SSMS has gone through quite a cycle since then. For example, with 2016 SSMS went to using the Visual Studio shell.

Have you, however, set up SSMS to treat .prc files as .sql files (as below)?

I just gave it a try and could treat a .prc file just like a .sql file. Opened it up in SSMS, could connect, and managed to execute SELECT @@VERSION; no problem. This, of course, doesn't change my opinion that you should save sql files as .sql files. 😉

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

schleep SSChampion Points: 12585 More actions · Answer 4

Yep, that's exactly where and how I set it up.

I've still got the 2K8 version installed as well, I'm guessing there must be some conflict.

Thom A SSC Guru Points: 99133 More actions · Answer 5

schleep - Tuesday, December 5, 2017 6:13 AM
Yep, that's exactly where and how I set it up.
I've still got the 2K8 version installed as well, I'm guessing there must be some conflict.

I have SSMS 2008-2017 install on my work PC, no issues.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

schleep SSChampion Points: 12585 More actions · Answer 6

We also have some very er... zealous :ermm: people making sure nothing happens without their permission in our computer settings and registries.
If they found out i'd installed SQL17...