This hack is about change buildup/bloat. When you ignore a particular DB’s schema drifts for a while, the amount of changes that the “Review” page needs to show gets larger and larger. Until, eventually, there’s simply too much content for it to handle, and it dies. This is a bummer, because you want to
ack those changes, but you don’t necessarily need to see them all in detail, as long as you have a general idea of what they were about.
So, this will be a tale of how I purged a set of un-acknowledged changes from DLM Dashboard for a specific Server/Database. RG support, bless their heart, wanted me to go to the document repo (which, if you’re not aware, uses a RavenDB back-end stored on your local file system) and purge everything. But I said no, I think we can do better than that.
Plus, if you really really care about those changes, you can use the RavenDB Studio (GUI) to dump the documents to CSV — i.e. if this tool is part of your audit/compliance toolbox and you don’t want to lose those changes, but you need to be able to “move on with life” by
acking the changes to the DB so that you can resume checking it on a regular basis without having a page-hang/crash.
This will be screenshot-heavy, censorship-heavy (to avoid divulging company secrets!), and meme-free (I know, I know, some of you will thank me and others will be a sad panda).
More to come, stay tuned!