-
Configure data retention per database
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.
1 vote -
Ability to see a list of objects changed within a drift set, and click that object name to jump to it in the page
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.
6 votes -
Ability to click the listed user on a drifted schema and filter to see just the changes made by them
Each drift shows the user who made changes, but you cannot filter to just that user's changes. Makes for a lot of scrolling.
7 votes -
Saving a schema name should be unique by category then by database.
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."7 votes -
Ability to review changes over time.
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.
4 votes -
6 votes
-
Ability to configure Dashboard refresh rate.
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.
31 votes -
Enable the list of changed objects to be collapsed
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 suffice25 votes -
Increase database/project limit beyond 50
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.
49 votes -
Suppress common event types that are not going to be actionable and frequently seen due to maintenance.
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 ('ALTERINDEX', 'UPDATE_STATISTICS'))
BEGIN15 votes -
Add Scrollbars to the what was changed
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 -
Track User Permission Changes for Auditing
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 -
Configure how many events are retained in main DDL_Events table
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 -
etseck vra oum knouck true !
etsa oum gre he nouck vra oum kclouck ok !
1 vote -
HISTORY. Simple way to compare past 14 days to current day and see what changed the most?
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.
4 votes -
Complete SQL of chages
Hi
Is there a way to get the whole SQL corresponding to all changes, in one file?
Thanks
Regards
3 votes -
Allow Duplicate schema names across pipelines
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 -
find/show the history of a single object
show find change history of single objects, (who, when and what has changed on an explicit object.)
61 votes -
It would be great if the hostname who made the change was included, incase people use the same login name
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
34 votes -
Removing server clean up!!
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
- Don't see your idea?