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. 6 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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  2. SQL Agent job tracking - I would love a way to add the master database. If simple alerts can be sent on drifts for agent job changes it would be fantastic.

    4 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 →
  3. It would be extremely beneficial to be able to send schema information to DLM Dashboard as part of an Octopus deployment, as otherwise every change to our integration database is being marked as a drift, even when the code has come through our CI process and deployed via Octopus. Ideally it would work just as the TeamCity one does - marking the changes as an update from continous integration.

    This makes the Dashboard far less useful for us as we can never know, without manual intervention, what version of the schema is in a given database at one time.

    7 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 →
  4. The Schema Version Name field should be wider. We are using labeld GIT Version Numbers including the latest commit SHA Hash ti identify a unique version. This combination looks like that:
    "5.1.2-alpha.44+Branch.dev.Sha.0dfb474d340d9a0c0aa4015204860c19122192bb"
    I would like to add this information as schema version name, but I can't.

    4 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 →
  5. Can some comparison options be added to DLM Dashboard to filter out things like NOT FOR REPLICATION? I feel we should have the same control as SQL Compare

    17 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 →
  6. We tried DLM Dashboard, but it doesn't work the way I hoped. I would love to authenticate only one standard database. Then DLM Dashboard can automatically show other related database's drift against the standard database. Instead, we have to approve each database's drift. I really hope DLM Dashboard can develop these kind of functions.

    9 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 →
  7. Suppress common event types that are not going to be actionable and frequently seen due to maintenance.

    These cause extra traffic and fill the history without benefit.

    Something like:
    DECLARE @eventdata XML = EVENTDATA();
    DECLARE @eventType SYSNAME = @EventData.value('(/EVENTINSTANCE/EventType)[1]', 'nvarchar(128)')
    IF (@eventType NOT IN ('ALTER
    INDEX', 'UPDATE_STATISTICS'))
    BEGIN

    15 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 →
  8. Please add the ability in the User configuration to setup a user login and password. Being able to access DLM from remote servers requires that we be able to specify a login and password, but the servers are not linked in AD so we cannot login. Only windows logins to local DLM server works. If we could add a user and password this would be great.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. The installation script should allow the DBA to configure how many events (rows) are stored/retained in the DDL_Events table. As-is, the install script checks for row-count over 512, and if so, deletes the last 420 rows. This should be configurable by the DBA, especially if he/she wants to be able to examine the "raw" event data written to the table instead of / in addition to using the Dashboard GUI.

    10 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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  10. Can you add the ability to track user permission changes at the database level?
    Example: I temporary give Joe write access to the database. I can accept the change in DLM Dashboard with the reason why the change was made in permissions.

    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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add the ability to have multiple email addresses notified when a change is made and allow notifications to be configured at a database level

    21 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  ·  Email Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  12. When the Email Alert is sent, allow the recipient to respond with an Acknowledgement via interface from within the email.

    For example, when the email is received that "DB has drifted", the email should provide a quick form for the recipient which mimics the Acknowledge interface from within DLM Dashboard. The goal would be to allow quick acknowledgement from the email itself, rather than having to access the UI.

    10 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  ·  Email Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  13. DLM Dashboad should have compatibility to use other database. Most of Time DBA has their own database to store their scripts. would be better if this feature gets added.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Some processes may issue DDL statements which will have a net-zero effect, it would be useful to exclude them. Here are some example:

    • stored procedure or SSIS package drops table and recreates it back exactly how it was including indexes.
    • a script drops indexes on staging table and then create them back, so net effect is zero.

    You may find a lot of such processes in Data warehouses. If you review the changes in the dashboard, then you see message "The changes made to this object can't be displayed. The object may have been rolled back." and a line for…

    18 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 →
  15. When the SQL Object "code" is really wide, it exapands the entire web page to the point of not seeing the "NOW" portion of the window. Can you add scrollbars at the bottom of the WAS and NOW portion of the web page for each SQL Object change?

    4 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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  16. I downloaded DLM and am super excited to begin using it. My only question/contention is the requirement of the Redgate database. I'm a developer with dbowner role in an existing database, but I don't have privileges to create new databases. So in future editions, expanding this software to be compatible/configurable with a database the developer chooses would be a home run! Thanks and all the best

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. I only want to see database drift if it is not in the previous pipeline environment. We have valid changes going in to our environments all the time through our CI process, I just wanted to see those changes that happen outside of that (which would be any change that has not been applied previously in the pipeline)

    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  ·  Flag idea as inappropriate…  ·  Admin →
  18. etsa oum gre he nouck vra oum kclouck ok !

    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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  19. The tool is currently alerting us to when triggers are enabled/disabled. The trigger itself isn't changing, just the status. It would be nice if the tool wouldn't see the this as a schema change.

    2 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  ·  Version Control  ·  Flag idea as inappropriate…  ·  Admin →
  20. For example we have a changeset like:

    Version 1.3: Add Missing Indexes

    And this script would be run on all pipelines but each Schema drift would have to be named differently which is just confusing for users it would be great to see the same name in each pipeline for the same changeset.

    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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?