Hi
I am using the Microsoft SQL Server Management Studio to manage our database objects over a VPN connection. At scheduled intervals the system saves recovery information.
The problem is that the location of the recovery files appears to be located on a remote server. This causes the UI to completely freeze while the operation is in progress.
How can I change the location of the recovery files or turn off the Auto Recovery functionality completely.
In VS2005 this is configurable in the Tools-->Options-->Environment settings.
Thanks.

Saving Auto Recovery Information
Jessica Alba
Hi everybody.
I'm having the same problem in Microsoft Visual Studio 2005, Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 but not only the IDE freezes when saving autorecovery information but also when saving any modified file.
Do you guys know of a thread like this related to this issue Any ideas
Thanks a lot!
XiaoYu
Bruce,
I have tried your fix on an XP SP2 machine and it seems to have worked. The only thing was that the reg key path for me (using SQL Server Management Studio Express) was:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\General\AutoRecover
Thanks.
JWTK
Hi,
IbrahimSA
Thanks for the reply.
Do you know when a fix may be released for this Are you aware of how I can get the Enterprise Manager working on the same pc as the SQL Server Management Studio or do I need to uninstall SQL Server 2005
Regards
David
scottm87
I haven't tried this but this registry mod should disable AutoRecovery. If it doesn't work let me know and I'll dig a bit deeper. All the standard disclaimers about registry manipulation apply.
Go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\General\AutoRecover and change the “AutoRecover Enabled” value to zero.
SanderV
There is not configurable today in SQL 2005. We have a tracking bug for this issue.
Thanks,
Gops Dwarak
chrisan
Enterprise manager and SQL Server Management studio can be run side by side on the same box. Answer is, you do not need to uninstall SQL 2005 to get Enterprise Manger working.
On the fix for the Autorecovery, it is planned to be fixed in next service pack. We are in planning stage for next service pack and to not have dates for this release now.
Thanks,
Gops Dwarak, MSFT