hello,
first, what do you mean by configurable? although the final details are still being decided, the intention is that the feature is always on by default with an option to manually turn it off for extreme cases (e.g. half the disk goes bad and it's better off that the entire database is restored as opposed to having mirroring ship tons of pages).
yes, automatic page repair will be available in both synchronous and asynchronous mode - there is really no difference between the two modes from the point of view of this feature, other than the delay one might get before the page is repaired, if the outstanding log send queue is very long in async.
as for availability of the feature in standard/enterprise, this is also still being decided, but all details will be in the final release documentation.
let me know if you have any other questions.
cheers,
kal.
|||That's what I wanted to know: The option of turning the feature off, and that it worked in both synchronous and asynchronous mode. I guessed that I'd have to wait to know if this is going to be an enterprise or standard-edition feature
That's not a feature, that's a Blessing!
I would not want to bless big customers and damn the others:-)
ok...2 days to go before vacations...
No comments:
Post a Comment