Very nice explanation thanks... could u please tell what happens in asynchronous commit and when the data in the log file will be deleted.. it gets deleted after updating to data file or after receiving harden acknowledge from secondary or both.... please let me know on this...
The logs will not be truncated unless the data is available in the data file. If you have a log send queue (logs are not hardened on secondary) or redo queue (logs are hardened on secondary but not yet redo to the data file) the logs will not be truncated. In both the cases you would see the Availability_Replica wait type. Async replicas behavior is only for commit (primary will not wait for ack from secondary to commit) the log truncation behavior is same. I believe understood your question correctly and answered. If not, please add your comment.
Thanks😊
Very nice explanation thanks... could u please tell what happens in asynchronous commit and when the data in the log file will be deleted.. it gets deleted after updating to data file or after receiving harden acknowledge from secondary or both.... please let me know on this...
The logs will not be truncated unless the data is available in the data file. If you have a log send queue (logs are not hardened on secondary) or redo queue (logs are hardened on secondary but not yet redo to the data file) the logs will not be truncated. In both the cases you would see the Availability_Replica wait type.
Async replicas behavior is only for commit (primary will not wait for ack from secondary to commit) the log truncation behavior is same.
I believe understood your question correctly and answered. If not, please add your comment.
Nice
hi Chandu is there anyway to connect with you on whatsapp ? amazing tutorial love it
You can contact me on, sqlwithchandu@gmail.com