I might have to get me a SSD to replace the original HDD in my system. Right now, I have the BI stuff all on a second WD Purple drive. But if a SSD would make the system more reliable, I could try imaging what I've got on the primary HDD to a SSD, move BI's database on the new SSD, and see how that goes.
I'm guessing that the database for BI gets a lot of thrashing? From using solid state NVRam over the years, we got conditioned to never use it for anything that needs to be rewritten very often because of the "wear out" of NAND type flash. I'm sure that's improved over time, but I still use new industrial controllers that have a warning to not re-flash the program too often because there's a 10,000 cycle write limit in their flash memory. So best to test new revisions in RAM and only flash when you're happy with things and ready to make the program more permanent.
I also remember reading that with older operating systems, you didn't want to let your Windows machine place its virtual RAM (pagefile/swapfile) onto a SSD. On a regular HDD, it was fine, but not on a SSD.
From what I've read, Win 8.1 and 10 handle this all correctly by default, but for Win 7 and below, you need to take some special steps to properly use a SSD. My system in question is running Win10, but I'm still queasy about the longevity of SSD for files that get rewritten too often. Is that issue completely a thing of the past now?
My system runs fine the way it is, and the CPU load is low, etc. But if it would be more reliable to replace the mechanical primary drive with a SSD, I'd probably do that. I just don't want to inadvertently make the system less reliable.
