Skip to main content
Database Administrators

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 5
    None of the practices you described are a good idea: shrinking data or log files shall have performance impact. If your files grow frequently, why don't you leave them with the appropriate size? And what benefits do you expect to have with the restart of the server/service? Commented Nov 7, 2019 at 15:26
  • 1
    Brent's blog has references to some very detailed articles on why you shouldn't be doing what you are doing. Paul Randall, Kim Tripp, Mike Walsh, Gail Shaw, and Tom LaRock all touch on different things. After you read those, then check this blog from Andy Mallon. Commented Nov 7, 2019 at 16:34
  • 2
    This is a legitimate set of questions, as evidenced by the numerous blog posts listed by @scsimon. That's why SE/SO exist. Why are people voting this question down? If you're tired of this issue (which is understandable), then either you can ignore the posted questions, or patiently continue answer them. We're all on the same path, just different parts of that path. I'm somewhere in the middle, and I get nervous asking a question here. Commented Nov 7, 2019 at 18:39
  • 1
    @ConradS. that's not completely the point I don't think. There are already numerous answers to this particular question accessible using the search function. Commented Nov 8, 2019 at 9:01