|
rjemison -> RE: Are there performance issues when SQL is unavailable? (4/3/2008 9:43:24 AM)
|
I have seen the same slowness regardless of whether the application is fully cached or not. My assumption is that because the stream server is available the client does not go into disconnect mode and is in essence timing out when trying to confirm the user still has access to the application. The quick fix for this scenario is to either have your db configured for high availability where it one node drops the other picks up, or to put in place a process where when SQL is unavailable the SG service on the stream servers is stopped, which will force the clients into disconnected mode. The negatives to this are that if something is not cached the user will not be able to get to it, and you will not be able to provision new applications until the SQL server comes back online.
|
|
|
|