SQL Server Home
SSMS tries to access disconnected network drives when in the Save File As wizard
as Won't Fix
3/13/2011 12:52:44 PM
User(s) can reproduce this bug
When saving files using the Save File As wizard, the underlying code is trying to connect to disconnected network drives. This results in extremely poor performance when using a slow network connection.
This behavior has been confirmed by many people, but I could not find a Connect item on it.
Every other application does NOT try to access disconnected network drives. Please fix this.
SQL Server 2008 SP1
Tools (SSMS, Agent, Profiler, Migration, etc.)
Windows 7 (all editions)
Operating System Language
Steps to Reproduce
Create a network drive, e.g. in your home network.
Go online using a slow network connection that cannot see the disconnected network drive.
Open SSMS and try to save file. Navigate around the directory hierarchy and it will take multiple seconds between each click, with the Save File As box going white and unresponsive in between.
The problem disappears if the disconnected network drive is removed.
It takes multiple seconds between each directory navigation.
Directory navigation does not take multiple seconds.
to post a comment.
Please enter a comment.
on 6/23/2011 at 6:08 AM
Thanks for reporting this issue.
We are sorry that you are experiencing this performance issue. SSMS 2008 SP1 uses Visual Studio 2005 Shell and we leverage File Save functionality provided to us by Shell.
This behavior is not directly controlled by us.
I have found related msdn connect issue which was logged against Visual Studio Shell team.
(Though this issue is reported for 2008 Shell, the same applies for Visal studio 2005 Shell)
I am going to close this issue as Won't Fix for now, if you have any concerns please feel free to re-open this issue.
on 3/13/2011 at 7:47 PM
Thank you very much for your feedback. We will look into it and get back to you as appropriate.
Microsoft SQL Server
to post a workaround.
Please enter a workaround.
on 3/14/2011 at 12:51 PM
As per Paul, the only workaround is to remove the network drives altogether.
© 2014 Microsoft