Timeline for Managing very large VLF
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2023 at 16:52 | comment | added | Sean Gallardy | And you would have killed every secondary replica which would now need to be reseeded as the switch to simple will obliterate your recovery forks. If the database is 50 GB that might be fine, larger it probably won't be. | |
| Nov 22, 2023 at 16:09 | comment | added | rvsc48 | If you had some down time, you could try removing the database from the AG, put it in simple mode, shrink the t-log on the primary (which should clear out the large vlf(s), then, place the db back in full recovery mode, and, then place it back in the AG. | |
| Nov 20, 2023 at 17:07 | history | edited | Erik Reasonable Rates Darling | CC BY-SA 4.0 |
added 6 characters in body
|
| Nov 20, 2023 at 17:01 | history | edited | Paul White♦ | CC BY-SA 4.0 |
added 3 characters in body
|
| Nov 20, 2023 at 14:47 | history | answered | Sean Gallardy | CC BY-SA 4.0 |