Search

SSMS loses its settings in certain condition by GrzegorzŁyp

Closed
as Won't Fix Help for as Won't Fix

2
0
Sign in
to vote
Type: Bug
ID: 775767
Opened: 1/4/2013 2:20:45 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
I open SSMS 2012 from the standard installed link. Open query window. Next I double click on the .sqlplan file and the next instance of SSMS 2012 is opened. When I close second instance the SqlStudio.bin file is overwritten with default settings (not mine). When I close the first instance the settings are overwritten again with proper values. The problem comes when I close the first instance and then the second one. In this case I lose my settings. The problem does not occur if on the second instance I open additional query tab.
Details (expand)

Product Language

English

Version

SQL Server 2012 - Developer Edition

Category

Tools (SSMS, Agent, Profiler, Migration, etc.)

Operating System

Windows 7 Enterprise (SP1)

Operating System Language

Polish

Steps to Reproduce

Open SSMS 2012 with query window. Change some settings. Close SSMS 2012. The SqlStudio.bin file should be overwriiten with new settings. Open SSMS 2012 with query window again. Open .sqlplan file with double click. New SSMS 2012 window should appear. Close first instance (with query window) and then close the instance with opened .sqlplan file. After opening SSMS 2012 with query window the settings are lost.

Actual Results

The settings are lost.

Expected Results

The settings should not be lost.

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/6/2013 at 11:49 AM
Hi!, thanks for writing in to Microsoft and reporting this bug.

We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this bug as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

Regards,
Sanjay Nagamangalam, SQL Server Manageability
Sign in to post a workaround.