Body: First, let me be clear, do NOT do this on a production server. Repeat after me, “I will NOT do this on a production server, or Todd will rip all the tags off of my mattresses.” Okay, now that we have that out of the way, let’s get down to it. A couple of times in the last week I’ve seen a question about culling a huge WSS_Logging database in a test VM environment. When you start considering snapshots and thin provisioned drives, a 3 GB WSS_Logging DB can be a real bummer, with almost no benefit to most people. The WSS_Logging DB is created with the Usage and Health Analysis Service Application and logs all kinds of usage information. Unless you’re testing that directly, it probably doesn’t do much good. However, having it around is probably good, in case anything you are testing uses it. I suggest a happy medium; leave it enabled, but reduce its overhead. That’s what this blog post will tell you how to do. By default the WSS_Logging keeps 14 days’ worth of information. That results...