How to troubleshoot a drift too big to show
krachynski
Posts: 14 Bronze 5
I have one rather large database (tiny by most standards, though) that is showing as having drifted to an unrecognized schema. Whenever I try to review it, my browser (Edge) idles for a long time then gives ma a blank page. It's rather like the schema change is just too big to display. I'd really like to accept this change because it was a valid one. Is there any kind of troubleshooting I can do to make that page actually succeed?
Tagged:
Best Answer
-
krachynski Posts: 14 Bronze 5I had to delete my RavenDB instance as it got too big to even index. The service would spend a bunch of time trying and then just shutting down.
Answers
It's only one of a dozen pipelines that fail to render.
Chrome is running hard on that tab, 36% CPU and 2gb of ram, then it eventually reloads.
One thing I noticed for this pipeline is that there's CLR objects that are trying to show a diff.
I'll look at filters as well. Too bad they are all manual, though.
Holidays kept me from worrying about this too much myself.