Allow configurable option to allow new connections to suspended Readable Secondary Database

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

Active

Type:	Suggestion
ID:	776528
Opened:	1/14/2013 2:13:31 PM
Access Restriction:	Public

Workaround(s)

view

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.

Details (expand)

English

SQL Engine

Far better would be to provide a configurable option to allow the administrator to decide behavior for the suspended readable secondary for this situation.
i.e. Default, Allow, Disallow (Allow would allow all connections, the latter would terminate existing and prevent any future connections)

Improved Reliability

Improved availability, administration, maintenance and configuration.

0 attachments

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.