February 8, 2017 at 12:38 am
Hi Robin,
No. Bulk logged recovery model will not work in always on. The database must be in Full recovery model before it can participate in an AAG.
--Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff878487.aspx
February 8, 2017 at 5:05 pm
Ricky Valencia - Wednesday, February 8, 2017 12:38 AMHi Robin,No. Bulk logged recovery model will not work in always on. The database must be in Full recovery model before it can participate in an AAG.
--Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff878487.aspx
Thanks Ricky.
February 9, 2017 at 10:24 pm
This was removed by the editor as SPAM
February 11, 2017 at 9:59 am
JasonClark - Thursday, February 9, 2017 10:24 PMBulk recovery does not able to capture changes on a transaction by transactions due to which risk of data loss chances are there.
I'm not sure what you're talking about. Under "normal" circumstances (like no AG, for example), If no minimally logged transactions are used, there is no difference between the BULK LOGGED Recover Model and the FULL Recovery Model. The log file can be used for Point-In-Time recovery.
The difference occurs in BULK LOGGED if ANY minimally logged transaction takes place. In that case, the backup file is marked as having had a minimally logged operation and, for restores, either the whole file must be restored or you have to stop the restore at the point in time prior to the start of this file. If you do use the whole file, then any log file restored after that that does NOT have a minimally logged transaction in it can be targeted for a point in time stop of the restore.
--Jeff Moden
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply