Fix the SQL Server Manager open file bug
When I click "Open In SQL Management Studio", I have the following reply from SSMS - translated from French:
The following files were specified on the command line:
D:\Documents
and
Settings\
...
\bbsilkof.sql
These files couldn't be found and won't be loaded
I suppose you should add enclosing quotes to the file name when emitting the command line. This should fix this.
-
Aaron Shumaker commented
It would be really great if in the generated SQL you populated the query parameters to. I.e. if I have variables being passed into the query, then the generated SQL should take a snapshot of the parameter values and set them on the @p1, etc. so that I can easily run the query in SSMS without having to lookup a bunch of ID's/values and set the params manually.
Even the "Open in new tab" within LinqPad opens a tab with a bunch of comments that aren't commented out so you aren't hitting the ground running when it comes to analyzing the SQL.
-
Tim McClure commented
I am having the same issue as reported previously
When I try to Analyze SQL via "Open in SQL Management Studio" I get the SSMS command line usage dialog. -
G. Richard Bellamy commented
When I try to Analyze SQL via "Open in SQL Management Studio" I get the SSMS command line usage dialog. I'm using the Beta 4.37.9.