When adding a pre-existing SQL User mapped to a SQL Login to a Database Role, the DLM exposes the password of the SQL Login. The change has nothing to do with the login. Even if the login was touched, DLM should mask the password. This is a severe security breach. Please fix this asap.

Hi team. I think that would be great idea that you sale some technical support for DLM, in my case after 6 month of use one day it didn't wo

When adding a new server it would be great to specify the default Category for databases on this server.

Adding Databases to the Dashboard on our DEV server would then automatically be added to the Development Category, rather than me having to select it for each one.

I have an idea, you should create a feature to help us convert sql query to logical chart. This is a useful feature for us

Incredible stupid you don't warn people a new db was going to be created, or give the option to put on a local server.

Stop page refresh. I can't get through even a short change without the page refreshing. If there is a way to turn it off, I can't find it.

I am using 'Category' to group my databases by data stage / purpose ('Reference' 'Application' 'ETL' 'Analysis'), and I would like to be able to assign a single 'reference' database to multiple pipelines.

It would be great to be able to color code categories so that they are easily identifiable in the pipeline view. For my use case, I have categories assigned to 'Reference' 'Application' 'ETL/Prep' 'Analysis' and I use my pipeline view to visualize the flow (I know this isnt the tool for lineage..).

Please make the Search feature consistent with Microsoft SQL Server Management Studio 2018. Thank you very much in advance!

I can't justify a tool that needs to place a new database on every server that I monitor. Either let me pick one location for the environment that can be placed anywhere, or have an option for a local express or file-based database. I really wanted to check this software out, but I can't...

It would be great if DLM Dashboard had a limit on how many schema versions are retained in the database. Some of my databases change more frequently than others. The limit should be a default across all databases with the ability to override the default value on a per-server or per-database level.

in the list of changes at the top you get a summation of what was change (2 tables, 2 stored procs, etc). would be nice to actually have those listed out by names, and have those names be a link to where you could click them and jump to that specific object's details lower on the page. in short, lessen the need to aimlessly scroll.

Each drift shows the user who made changes, but you cannot filter to just that user's changes. Makes for a lot of scrolling.

Enable editing change server name or credentials in configuration panel for existing servers

A series of changes are shown. The DBA can either approve them, or decline them, and if decline, run reversal scripts as needed? May be too complex, but would be wonderful!

I added a dumb test table. Red Gate caught it. Then I deleted it. Red Gate seemed to get lost. If the change and then removal/reversion could be tracked somehow possible, meaning this was a non-event, that'd be great.

a pause button should be useful for Configuration\Servers\Databases or Servers screen. Somtimes we need to pause tracking db or server. But there is no option except edit/remove

I would like to be able to tell DLM Dashboard not to alert when constraints don't match or are disabled. I manage a few databases where we disable constraints for data imports and then re-enable them afterwards. This is resulting in 2 email alerts per data load and training me to just ignore the alerts.

Would it be possible to tell DLM either ignore constraints or don't alert if the constraints are there but no enabled?

ELK, Splunk, and Appinsights are better than email