Danger with the Explorer window in SQL - by Björn Baecklund

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 788422 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 5/22/2013 11:55:03 AM
Access Restriction Public


Recently I ran into a dangereous situation with SQL 2008 R2. 
I had 2 Serverers connected at the same time in Explorer (left)window.
One in production and the other on its way to become in production.
I had created a backup and a restore skript to use during migration.
I started the backup script and all went well, closed the script
And opened the restore script and ran it ON THE WRONG server.
Sign in to post a comment.
Posted by Microsoft on 5/28/2013 at 11:02 AM
Yes, perfectly readable. Thank you, Björn. The change you propose to protect users from accidentally running scripts against the wrong server is too large for a servicing release to an existing version of SQL. As such, this DCR Connect item will be closed as Won't Fix. We have added the suggestion to future releases of SSMS, and will make it available for revisitation when we start our next cycle at the drawing board. Thanks for your suggestion. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Björn Baecklund on 5/28/2013 at 5:05 AM
Hop this is readable english /:
Posted by Microsoft on 5/23/2013 at 1:32 PM
Hello Björn. Apologies, but we have been unable to effectively translate your DCR. Is there any chance you could update this or create a duplicate in English, or should we see if we can work from automated translations? -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)