If I already have a single drive failure, should I even consider trying to upgrading the firmware on the rest of the drives or the RAID controller? Seems to work but one thing we NEVER do is roll out firmware at the same time as other updates like drivers/code etc. I might be going against the grain here, but if it's not broken don't fix it.If it's not a security issue then I leave it alone. Perhaps you can schedule the utility once a month, then update them with other reboots?
I like to call this role the "involuntary DBA." The focus of this article is to provide a primer of database maintenance best-practices for all the involuntary DBAs out there.
As with the majority of tasks and procedures in the IT world, there isn't an easy one-size-fits-all solution for effective database maintenance, but there are some key areas that nearly always need to be addressed.
In log files, it can have a much more significant impact on performance, especially if auto-growth is set to increase each file size only by a very small amount each time it is needed.
Log files are internally divided into sections called Virtual Log Files (VLFs) and the more fragmentation there is in the log file (I use the singular here because there is no gain from having multiple log files—there should only be one per database), the more VLFs there are.
Instead, this strategy triggers a full index rebuild when a full publish process has completed.
When you attach this strategy to an index, you will see the following message in the You should not combine this strategy with the Synchronous Strategy, but you can combine it with any of the other strategies.Because this strategy causes a full index rebuild, you should combine it with the Switch On Rebuild Lucene Index or the Switch On Rebuild Solr Search Index.When you use this strategy in combination with the On Publish End Async strategy, you need to register it as the first entry in the list for it to be triggered first: setting.All the strategies that are delivered with Sitecore are defined under the following node in the event and it triggers a full index rebuild.In a distributed environment, the index rebuild is triggered on all remote servers where this strategy is configured. In environments where a full publish is required to run regularly, you should not trigger incremental index rebuilds because this uses a lot of resources.• Weekly – Clean windows inside and out, dust fixtures, wipe smudges from doors and walls.