0

I read several articles recommending switching to Simple recovery model before shrinking dbs. Here, here and here.

Please explain me - Why it is needed.

I also read the white paper about Maintenance of SharePoint Databases - there is nothing about switching to Simple model.

Our SP dbs configured to Full recovery model. DBA tried to shrink db on dev without switching to Simple recovery model. Shrink was done smoothly without any issues.

P.S. I know that shrinking of SP databases is not recommended, but sometimes it is needed.

| improve this question | |
0

It shouldn’t be needed. Switching to the simple recovery model breaks the backup chain of transaction logs which may be worse than having the shrink recorded in them.

Are you referring to the data files or the transaction logs? Shrinking the TLs is trickier as it heavily depends on how many pages are free (have been backed up) at the end of the log file.

| improve this answer | |
  • Greg, thank you for the answer. I am about shrinking transactions log file. – Raf Mar 11 at 11:07
  • Yeah, they’re a lot trickier. There’s plenty of pages on the net describing why shrinking the TL doesn’t free up as much space as you think. – Greg W Mar 11 at 11:09
  • We tried to shrink db log files on dev env and it was free a big amount of space – Raf Mar 11 at 11:12
  • It all “depends”. If you’re in the full recovery model, you can’t shrink the TL at all unless it’s been backed up. – Greg W Mar 11 at 11:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.