I’m using the Toad for SQL Server 5.0.0.444 Freeware.
I spend time 1 sec less for connecting a local server…
but other server(not include intranet) connecting time is 2 min over.
Do you have any toad settings or server settings for speed up connection?
p.s Microsoft SQL Server Management Studio connection time is 1 sec less for other server.
p.s SQL Server version is 2005 in Windows 2008 server.
Unfortunately this is a know deficiency. it is being addressed in Toad for SQL
Server 5.5. The time is being spent polling services available on the server
(Which you probably don’t have access to at all and so the requests time out).
/Henrik Johnson
Quest Software
Ok, we experience the same problem here, Toad 5.0.1.554 times out on Synch (even when the connections are already opened in the manager). Is there a workaround and is the planned release date of 5.5 already known?
I have had the same issue with some server instances on the same VM, but not
with others and I have full ADMIN rights…
I use the re-connect and all is well. Every blue moon I have to restart Toad-ss
5.0.1 but it is rare.
Hank Freeman
Senior Systems, Database/Data Warehouse Architect
678.414.0090 my cell Primary
I have had the same issue with some server instances on the same VM, but not
with others and I have full ADMIN rights…
I use the re-connect and all is well. Every blue moon I have to restart Toad-ss
5.0.1 but it is rare.
Hank Freeman
Senior Systems, Database/Data Warehouse Architect
678.414.0090 my cell Primary
Guys,
We do work on patch to address some of the issues. We are targeting patch at the late November. This issue should be solved in the patch.
–
Valentin
Hello,
After some investiogation we have found that in such environment when Toad and SQL Server not located in one intranet we can reproduce such issue. But it is only actual if you use Tree List vew in Object or Database Explorer. Therefore you will have such long connect if ObjExp or DBExp automatically opens on every new connect.
As workaround I can suggest to not use TreeList view.
Please confirm that it helps in your case or provide other details.
thanks for your input,
Alexander Maximov
/Quest Software
Want to update you on this subject - from our perspective this issue was solved in 5.0.2 patch. Target date is at the end of November.
Message was edited by: Alexander.Maximov