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?
Comments
11 comments
-
No? I'm still having trouble trying to acknowledge drift in one of my schemas. Any browser will fail as the server times out trying to render the output. I just checked for a new version and it seems that today's installer says I'm on the latest already.
-
Is it just reviewing the changes for one of the databases? Do other dbs/instances work fine?
-
One specific database. I have several other pipelines that are working fine.
-
I'm having the same issue, DLM Dashboard 1.7.5.1116
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. -
So I applied a filter to the pipeline to ignore Assembly changes, and after restarting the DLM Monitor services, I was able to acknowledge the drift.
-
-
What "non manual" filters would you like? Apologies for the delay. Holidays got in the way.
-
Well, you can't specify the filters in DLM Dashboard directly but have to load a file. That's the manual part. I'm not sure how to visually build that file.
Holidays kept me from worrying about this too much myself. -
Ah, that makes sense. We use the same filters everywhere, and tend to just expect people to build one in Compare. Not sure we'd add a web based one, but being able to click on a "type" of object and add a filter quickly would be nice. Not sure I could get a developer to add this, but I'll ask.
-
I'll poke around Compare then.
-
I 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.
Add comment
Please sign in to leave a comment.