When acknowledging changes, it appears that you can't use the same schema name across databases in different categories.

Example:

Development
MYDB
Save schema named '01/09/2018'

Production
MYDB
Save schema named '01/09/2018'
** Result in error "There is already a schema saved with this name."

Not able to amend the comments provided while reviewing the Schema changes.

Our test environment can't see live, however we do get daily DACPACs from LIVE. Would it be possible to select a folder to use as 'live' rather than a server so we can compare to the Live DACPAC rather than the server?

I would like a way to enter an object name (stored proc, table,...) and see the changes that have occurred over a specific time frame whether or not the changes have been accepted.

This polling process creates a fair amount of network traffic over time and for bandwidth limited remote sights that can cause an issue. Having ability to control how often (and when) schema changes are checked would go a long way in reducing this issue

I use IP addresses for dev/qa servers. Having a friendly name would be helpful at a glance

Hi Redgate Team,

I would like to report a bug. I am running the latest version of DLM Dashboard at the time of this post. I have added many databases to the dashboard. I have decided I no longer need to monitor one of those databases so I went to the configuration tab and removed it completely. However, it is still showing up on my dashboard. When I click on it, it does not give me any information. I would expect this database to disappear from the dashboard after removing its configuration.

I just did a new release which had a lot of changes in it. Now I can't acknowledge those change because the refresh rate of the system is to tight. Either need to be able to turn it off for a bit or change the rate so that I have time to put a version number and comment in and click acknowledge.

It would be useful if the changed objects could be listed without the T-SQL code being displayed.
Some form of a toggle switch so that the code could be hidden/displayed would suffice

There must be many users that would want to migrate the entire installation and history to a new host. But we can not find any help on this.

The screen is constantly refreshing, and will refresh away before I'm done entering my comments. This is very frustrating!

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.

The 50 database limit makes this product a non-starter in our shop. We have over 300 databases that need monitoring. We would even be willing to pay for a 'Pro' version of this product if this limitation was removed.

If there are differences the system could suggest that a schema compare be done on the databases.

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.

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.

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.

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.