I cant seem to see more than a couple hours EVERY CRISIS like what we just had and found to be the SAPHOS Client, but everyone was claiming it was SQL, what changed last week compared to today/?? I cant provide that.

It would be great if the hostname who made the change was included, incase people use the same login name. We have developers who all use the same login e.g. developer so seeing who made the change is not possible, as it says login name developer but can it also include hostname e.g. pauls-laptop

Ability to post review using command line utility or web-service call.

Hi

Is there a way to get the whole SQL corresponding to all changes, in one file?

Thanks

Regards

When reviewing a drift in sprocs running hundreds of lines of code, it is hard to find the line that changed because the UI presents the full file with no links or shortcuts to the changes. Since the full SQL statement is available as a download, the UI should only show the changed lines and maybe +3 lines above or below for context.

So we have specific groups that work on certain projects/pipelines. The ability to configure email notification groups based on the pipeline there're working on would be awesome i.e. group A working on pipeline A only gets pipeline A drift notifications. Group B working on pipeline B only gets pipeline B drift notifications

I'm unable to configure email alerts right now because of how our certificate and DNS are configured, which results in name mismatches--if I use the correct name that resolves to an internal address, I get a certificate name mismatch. If I use the name on the certificate, I end up connecting to the wrong IP address. Thus, the only way I can configure alerts is to disable the secure connection, which I don't want to do. It would be nice to have some other options here so I could work around the certificate name problem.

I have installed a filter that excludes all User and Role changes. However, a SQL GRANT EXECUTE TO user statement appears as an Update. The type is Unknown. Is it possible to filter these out as well?

On all tabs, particularly the Home tab, there is way too much wasted screen real estate. On my 1920*1080 resolution monitor, I can see a whopping 2.5 rows (pipelines) at once. That's ridiculous.

I currently have to login to the DLM Dashboard every time I reopen the browser. I don't have to do this with SQL Monitor. I want the DLM Dashboard login to persist in a similiar fashion to SQL Monitor

Please expand the filter documentation to have an example for each type of filter available.

Also, allow me to filter out those changes that are listed as " The object may have been rolled back." We drop indexes and then rebuild indexes as part of daily data loads. I don't need to see this in the list.

Allow DLM Dashboard to seamlessly support databases that are in Availability Groups.

Currently, you have to create the objects on one server, then fail the AG over to the other servers, and recreate the objects there. Otherwise, when the AG is failed over, DLM has problems.

Ideally, this process would be seamless, behind-the-scenes (or maybe with a prompt to the user configuring the DB for use with DLM Dashboard to indicate that the DB is part of an AG, and therefore the process will also run against the other servers).

(Logged off the back of a support ticket 55607)

Show differences between prod/test/dev/uat environments and track these changes.

It would be nice to have an option to ignore column order and index order

I would like to be able to bulk acknowledge the same changes made to multiple databases in a pipeline.

Add a filter option for jobs by APP_NAME

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.

Currently when we see a new table, the NVARCHAR columns also specify the collation that they are using. If the collation was not specified and the default is being used, I would like to not see the collation in the diff shown in the dashboard.

This is likely an issue in more places than just new tables, likely other spots with (N)VARCHAR columns.