DLM Dashboard

DLM Dashboard (previously called SQL Lighthouse) is a tool that monitors your database schemas in order to alert you about unexpected changes – often called database drift. Once alerted, users can choose to take remedial action. This might be to rollback the change, apply it to another database or script the change into version control. To find out more about what DLM Dashboard does and how it works, please visit our “website”: http://www.red-gate.com/products/dlm/dlm-dashboard/.

If you have any questions or need help with Redgate’s free tool DLM Dashboard, please visit our “support forums”: http://www.red-gate.com/MessageBoard/viewforum.php?f=176.

DLM Dashboard

Categories

JUMP TO ANOTHER FORUM

  1. Right now (and admittedly I've not tried it but I've looked at how it works) it looks like the Dashboard knows nothing about full fledged 'official' deployments and requires you manually approve each change made via the DLM automation suite (e.g. Octopus).

    If this is the case, then in order to be part of the suite it MUST be able to track these changes and label accordingly with no user intervention.

    For me, this dashboard is ONLY useful if it tells me about unauthorized changes - I care not a jot about ones made by Octopus since, at that point,…

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  History  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently working on an API integration between tools in the Automation Suite and the dashboard. Our aim for the feature is to be able to do exactly this – picking up version numbers from your Continuous Integration/Release Management tools and auto approving changes from your approved pipeline.

  2. I'm not sure I like the Project >> Environment >> Server >> Database hierarchy.

    The way the check works doesn't make sense to me with the suggested categorization hierarchy.

    If I have a project (P1), with an environment (Prod), a server (S1), and 3 databases (D1, D2, D3). All of these databases are part of the same project (P1).

    Then another environment of (Dev) with the same databases on another server. I want to compare the respective Dev D1 to the respective Prod D1. That's how it logically organizes to me.

    I add the databases that way and it will…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We’re planning to improve the way you can organize database later this year. The current projects mechanism is limited. Please do leave us any comments with your thoughts on how we can make this better

  3. It would be really nice if Lighthouse had the ability to push change notification to external systems, e.g. Slack.
    This could either be acomplished with a http post functionality, or with a general powershell script support.

    51 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently thinking about the best way of implementing this. I’ve actually just blogged about how you can integrate DLM Dashboard with many other services / systems using the existing email notifications system and Zapier (http://blog.red-gate.com/dlm-dashboard-and-service-integration/). I’d love to hear what kind of use cases you have, and also whether the email/zapier approach addresses these at all?

  • Don't see your idea?