Search

SSMS : too dependent on network responsiveness by aaronbertrand

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
 to vote
Type: Bug
ID: 346679
Opened: 5/28/2008 8:51:07 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
If I have SSMS open against a remote server, and then lose connectivity, all of the operations I try to do within the query window and other areas are severely delayed.
Details (expand)
Product Language
English

Version

SQL Server 2008 February CTP

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Windows Vista SP1
Operating System Language
US English
Steps to Reproduce
Establish a connection to a remote server. Type a few queries, run them, initiate a . Now sever the connection (unplug the network cable, disconnect from the VPN, etc.) and try to edit your queries.
Actual Results
Clicking on tabs, typing, etc. are all severely delayed. I am not sure if it is constantly trying to connect to the remote server or what is going on, but clearly it is related to the lost connectivity.
Expected Results
I should be able to continue writing code without an active connection. I should not notice my connection has been severed until I actually *lose* connectivity.

Platform

32
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 6/20/2011 at 1:19 AM
Hi Aaron,

This is regarding connect item 346679. We are not able to reproduce the issue in the current version (Denali) and hence are closing the connect item as NR. However if you can see the issue in any Denali release, kindly let us know and we will re-evaluate.

thank you

Seshagiri
Posted by Microsoft on 5/30/2008 at 4:59 PM
I can certainly rule out the size of meta data and script size.

Eric
Posted by aaronbertrand on 5/30/2008 at 8:19 AM
In this specific case, 1239 objects, 160 tables, script size ~3K.

However, I notice the same symptom no matter which database or server I am connected to. The common thread is that SSMS is clearly trying very hard to do something over a connection that no longer exists.
Posted by Microsoft on 5/30/2008 at 8:00 AM
Aaron,

I think someone closed it as a part of release management. I have reactivated it to better understand the case in the latest build. Can you share more information with me?

1. Number objects in sys.objects and sys.tables
2. size of script file


Thanks,
Eric Kang
Program Manager, Microsoft SQL Server
Posted by aaronbertrand on 5/28/2008 at 9:24 AM
Wow, that was quick. No comment? :-(
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement