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. When Dashboard is setup the default database name is Redgate, this doesn't always fit in with our database name standards. The ability to choose the name would be useful.

    9 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  ·  Flag idea as inappropriate…  ·  Admin →
  2. I know we can filter schema changes via a file as here:

    http://documentation.red-gate.com/display/DDB1/Using+filters

    However, it'd be much easier to deal with if we had some UI around this which would generate the config that DLM Dashboard would use transparently.

    23 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  ·  Flag idea as inappropriate…  ·  Admin →
  3. We utilize partitions which alter the table as part of intended functionality and are not schema drifts. It would help to be able to have these changes not show up as drift.

    7 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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Page automatically refreshes while reviewing schema changes and makes it difficult to review changes. Please include an option to disable refresh on the difference review pages, e.g.: localhost:19528/#/differences/DbObservations-483

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. So I decided I didn't want to monitor a certain server no more so removed the server from my list but it has not removed the RedGate database, and I guess therefore hasn't removed the DDL trigger etc.... This is just utterly ridiculous and really needs urgently changing. That's the DLM Dashboard now uninstalled..!!!

    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  ·  History  ·  Flag idea as inappropriate…  ·  Admin →
  6. I accepted a change only to realise this change shouldn't have been made so I want to be able to undo/delete my acceptance of a change.

    If I undo the change on SQL, then I then have two schema changes instead of zero!

    3 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 →
  7. Show differences between prod/test/dev/uat environments and track these changes.

    45 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 →
  8. As the teams are more and more agile it requires the db changes to be deployed to production as soon as possible with out having any down time in production. We need to have a mechanism to ensure that both additive and contraction changes in DB will not require any down time in production and wont result in data loss and will guarantee that business continuity is ensured during deployment.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. At present set up scripts needs to be run in each environment which requires certain elevated privileges in each environment and needs continuous tracking. As the schema does not change often can we have an option to track every 30 minutes read only pull from server than push from the server based on triggers? We want this tracking to be non intrusive to the system that it wont add additional resource overhead and happens in a controlled way

    12 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  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add a function to export any give schema verision to you can setup different DB stages quickly.

    23 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  ·  Flag idea as inappropriate…  ·  Admin →
  11. It would be nice if the tools could detect DELETE on a database or even better on a specific table.

    5 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  ·  Flag idea as inappropriate…  ·  Admin →
  12. It would be nice to be able to have ex. testing before integration...

    13 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 →
  13. SELECT '[' + s.name + '].[' + o.name + '].[' + i.name + ']' AS keyname
    FROM sys.foreignkeys AS i
    INNER JOIN sys.objects AS o ON i.parent
    objectid = o.objectid
    INNER JOIN sys.schemas AS s ON o.schemaid = s.schemaid
    WHERE i.isnottrusted = 1
    AND i.isnotforreplication = 0
    AND i.is
    disabled = 0;

    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 →
  14. I think it might be a good idea to detect when index is disabled. I know that it might not surface when comparing schemas, but the effect of disabling is on querying the given table is comparable with an index beeing dropped or modified in an unfortunate way.

    Not to mention that there is no way to tell from SSMS GUI whether index has been disabled or not

    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  ·  Email Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  15. There must be a way to moderate alerts such that they are not trigger reed on every event but rather aggregated so that we receive an email say on a given interval - such as a specified time or say at 6 hour intervals.
    Our sys admins are getting concerned about the traffic coming from my ip which is monitoring several MSCRM dev/test environments and the emails can be too frequent especially when there is a tear down and rebuild etc. also the event cache in the Redgate db retention needs to be expanded and configurable.

    6 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 →
  16. Some times multiple changes occur for a database that are unrelated before a new schema can be acknowledged. I would like a method to select or group selected changes and acknowledge those changes as a particular schema while leaving the unselected changes available to be added to a different schema history.

    34 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 →
  17. I would like to Redgate work with the Netezza platform.

    12 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 →
  18. 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 →
  19. Plain text search of changelog.

    Really excellent software from RedGate (I'm never disappointed).

    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 →
  20. At the moment, the UI seems designed to be very manual and interactive, ie, a change happens, and it requires someone to acknowledge the change or deal with it. This is good, and will definitely be useful for some environments.

    However, I suggest that there be another workflow added, based around CI driven changes. In this mode, the "acknowledge change" functionality would be hidden, and all changes happen via the integration with a CI tool.

    Once a database is built via "SQL CI Build", it is automatically detected as an accepted change, and as it progresses through environments (via "SQL…

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