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. the ability to view all changes since a certain date would allow a DBA to migrate or roll back schema changes

    65 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  ·  Version Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Before loading the Differences screen, have options pre loading for filtering. When loading this page, DLM will often give a list of every single View in the database, with the statement "No details available", which causes a huge load of the web browser (Firefox, with just this page open and DLM is using over 2Gb!). It also means it takes a very long time to load the page, and makes it impossible to actually tell what changed.

    10 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  ·  Version Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Perhaps I'm not using this correctly but I need to update multiple dbs to a certain schema. Ideally I'd use the same name in the field "Name this schema" when I'm reviewing the change so I can track that the dbs are indeed at the same schema version. Or perhaps there's another way to do this?

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    The dashboard spots when two databases have the same schema. If you name it on one database then the dashboard should automatically give the name to your second database. If it’s not doing so then you may have uncovered a bug in the tool – please could you email dlmdashboardsupport@red-gate.com and we can work out what’s happening?The dashboard spots when two databases have the same schema. If you name it on one database

  4. t would be nice to have the functionality to create ONE FILE containing ALL the changes that have been done to cause a certain drift in the database version. I noticed currently it gives me the option to download a file for each change done individually, but very often these changes can amount to quite a large number, and having to download hundreds of files is not really practical.
    Having all the changes "downloadable" as one file would be a huge benefit.
    Adding more to that functionality, as I've already seen people suggested: to have the option to "pick and…

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. I want to be able to add hotfix changes made in production into source control, so that they don't get deleted when I next deploy

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Instead of showing 'schema not recognized' automatically generate a name for that state, for example a version number like v1, v2, v3 etc.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I don't want to have to keep naming the states of my databases. It should automatically use the revision numbers from my version control system

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. I want to check that our dev server is in sync with version control. I want to show the head of my version control system as an environment, so I can see it side by side

    158 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?