How are people handling the limit on DLM Dashboard?

batcheck

We're starting on our journey to DevOps our databases. I showed a bunch of developers DLM Dashboard and everyone is very excited to at least see the drift even if they are not ready to implement SQL Change Automation. However, we have about 130 databases per tier (Dev, QA, Stage, Performance, Production) that in theory could leverage DLM Dashboard.

How are people managing the limit of 50 database per install of DLM? Do you just have a massive sprawl of DLM Dashboard VMs in your environment? Is it possible to install DLM multiple times on a single host with different ports and backend databases?

In my case right now we're talking about a potential 13 installs of DLM. That's nuts.

Thanks,

AlexYates

You are right, that is nuts.

EITHER: One DLM Dash install per team and the team is responsible for maintaining it - but that relies on each individual team having a neat division of responsibilities and not needing to look after more than 50.

OR: Set up an automated process to drift check before deployment.
https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments/handling-schema-drift

OR: Build your own thing with triggers:
https://www.red-gate.com/simple-talk/sql/database-administration/database-deployment-the-bits-database-version-drift/

OR do several of those.

But 13 instances of DLM Dash really is nuts if there are people who will need to look at many different instances.

batcheck

Alot of it is self inflicted. One of the teams decided to have a single database per state for rulesets. It is however all custom development and drift is a major problem as we promote.

Thanks Alex, I'll look into those suggestions

AlexYates

Oof, that sounds fun. Good luck!