Allow configurable option to allow new connections to suspended Readable Secondary Database - by retracement

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 776528 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 1/14/2013 2:13:31 PM
Access Restriction Public

Description

When a Readable Secondary Database is suspended, by design new connections are not allowed although existing ones will succeed returning data as of the point of time of suspension. See the following url as reference http://msdn.microsoft.com/en-us/library/ff878303.aspx

Whilst this might be desirable behavior in some cases, it is not necessary the desired behavior in others. 
Sign in to post a comment.
Posted by retracement on 1/15/2013 at 1:01 PM
Please also refer to this MSDN forum question and the initial questions and my responses. http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/cf767e57-903d-40aa-9bf0-91def96af4b6
The poster question relates to the difference in behavior of reading readable secondaries for new connections between suspending movement on the primary and suspending a readable secondary. Please see my explanation. I believe that the behavior of suspended readable secondaries should be configurable for either situation.