We built a new SIM installation earlier this year (updated recently to latest version of 7.4.x), got it up and running successfully, and all was well. Then everyone involved got sidetracked on other projects while SIM ran just fine on its own. We are using SQL Express, as SIM has redundancy in our environment and we didn't feel a need to burn money on another SQL license. (The redundancy is via the HP monitoring plugin for SCOM).
Fast forward 8 months. Our SQL Express database hit the 10gb mark, which is the maximum size allowed. It cannot grow and has gotten into a problematic state.
We can logon to SIM, but there's no data in the interface. The database can be managed via SQL Management Studio. To be perfectly honest, I don't really care about historical data and wouldn't have a problem with building a new database from scratch. In the interest of going through some valuable recovery management exercises, I'd at least like to take a crack at "fixing" this.
My definition of "fix" is this: Shrink the database below 10gb and manage it better going forward to keep it clean via automated tasks. I'm aware of how to schedule tasks to delete events older than X number of days. I can't at the moment though, because the database is in a state where events cannot be managed via the application GUI (there's no data presented). I'm assuming that events also can't be managed via SIM's command line interface as well while the database is locked at its current size.
What say you? Shrink it below 10gb via SQL Management Studio, then try to access data within the interface and purge all junk older than a month to reduce its size naturally?