GUI Display in Professional Edition Questions

• 
  Thank you for your post into the forum.
  
  Unfortunately I have been unable to reproduce your fault symptoms where one monitoring workstation kicks out another monitoring workstation.
  
  What is the OS and service pack level of each workstation?
  
  Many Thanks
  Eddie
  
  Eddie Davis
  Red Gate Software Ltd
  Technical Support Engineer

  Eddie D June 15, 2007 10:49

  - 0 +
• 
  Both workstations are running Windows 2003 Service Pack 2. They also both have SQL Server 2005 Service Pack 2.
  
  I am not sure if the problem is that one monitoring workstation is kicking the other workstation off, or if the workstations simply periodically disconnect from the monitored servers.
  
  Most mornings when I check the monitoring workstations, at least half, if not 3/4 of the monitored servers are showing as disconnected and I have to manually refresh the connection on each of them.

  rgiesbrecht June 15, 2007 10:53

  - 0 +
• 
  I also notice that periodically my connections are disconnected and nothing short of a manual refresh will restore them.
  
  Marc

  marclallen June 15, 2007 11:13

  - 0 +
• 
  Hi, I had similar problems with my local machine and occasionally a development server disconnecting and showing a timeout error - albeit with SQL2K
  
  It turned out to be because each Server contained several DBs that had the AUTO_CLOSE option set to ON.
  With this set ON, each DB is closed after the last user exist it. Everytime the database gets accessed it has to reopen and this can be a slow process.
  
  I am guessing that SQL Backup will effectively try to reopen each database when it refreshes its connection to a server and so it takes a while to start them all up.
  
  This can also cause Enterprise manager to be very slow when you try to expand the Databases node or even the drop down Database combobox in Query analyser seems to go slow if any of the DBs are set to AUTO CLOSE.
  
  Have a look in the SQL Server Logs to see if you are getting many 'Starting up database xxxxx' messages...

  martinb1000 June 19, 2007 11:06

  - 0 +
• 
  Sorry, but Auto Close is not the solution. I always disable Auto Close when I create my databases.
  
  I have a feeling that timeouts may place into this, but I am not sure what setting I would have to change.

  rgiesbrecht June 19, 2007 11:12

  - 0 +
• 
  Have you tried increasing the connection timeout property for each registered server - right click on the server name and select edit, connection properties tab... That may help?

  martinb1000 June 19, 2007 11:38

  - 0 +
• 
  Are you talking about the connection properties tab in Enterprise Manager/SQL Management Studio or in the SQL Backup GUI?
  
  So far, it only seems to be SQL Backup monitoring that times out. Everything else is working fine.

  rgiesbrecht June 19, 2007 11:44

  - 0 +
• 
  In the SQL Backup GUI...

  martinb1000 June 19, 2007 11:47

  - 0 +
• 
  Thanks, I finally found it (had to search under Edit when you right-click on the registered server) -- somewhat counter-intuitive.
  
  I will play with various timeout values to see what works best.

  rgiesbrecht June 19, 2007 11:55

  - 0 +
• 

  rgiesbrecht wrote:

  Thanks, I finally found it (had to search under Edit when you right-click on the registered server) -- somewhat counter-intuitive.
  
  I will play with various timeout values to see what works best.

  
  Oh boy.. I'm resurrecting a 2 yr old dead post. But I just hit this issue!
  
  Why can't we have a simple REFRESH ALL connections option?

  slick84 July 20, 2009 16:58

  - 0 +

Add comment

Please sign in to leave a comment.