164 results found
-
Allow meta tagging of changes
Add ability to tag a change with user-defined tags. Examples can be development tasks or projects that the changes relate to, etc.
3 votes -
Exclude tempDB from wrting to the Event table
We use tempDB extensively, creating tables, deleting tables and building indexes. It creates a lot of noise in the Event table. The trigger should exclude DDL activity in tempDB from being written to the Event table.
3 votes -
How email alerts are grouping the changes?
Hi! Some times I'm receiving an email for each change in any object in same Environment/Database, if my team modified 3 stored procedures I received 3 emails, but some times I'm receiving only one email...
It depends of the difference of time between each change.. or depending of the user... ?
What is the criteria to group the changes in email alerts for the same Environment/Database?
So my idea is to have something to edit this feature.
Thanks!3 votes -
Tray notifier for problems, just like Visual Studio TFS Build notifier
I would very much prefer "silent" notification, instead of an email.
I guess it would require a server side component, but benefits are also, that all team members could get immediate notification this way.
Like TFS, the icon in the tray area, could shift icon/color, when troubles are discovered.2 votes -
Ability 2 Move Lighthouse ProgramData Directory Off C:\
Move the C:\ProgamData folder for lighthouse to another drive to save space.
10 votes -
Milestone versions
I'd like to be able to mark certain states as being milestones. These are important states that I'd like to see a history of
3 votes -
Automatically generate names for unknown states
Instead of showing 'schema not recognized' automatically generate a name for that state, for example a version number like v1, v2, v3 etc.
1 vote -
Add a database role to the add database set up
When you add a server could you create an SQL Account for the application to use? This would assign the basic minimum permissions that are needed. This should be fairly easy as the set up has to be done by someone with sysadmin to the server. The details could be stored in the RedGate database, against the server with the password encrypted or hashed.
Then when you add a database it could create a role and add the application account to the role as part of the setup to make it quicker.This would streamline the setup procedure, but you…
1 vote -
Rescan upon database restore
Automatically scan a database for schema drift upon database restore. SQL Server logs should be able to trigger that response instead of a periodic scan.
43 votes -
Report on Server Level Config Changes
I would like to see server level config changes be recorded, with information like before and after config values and who made the change. Items like min/max memory, etc.
53 votes -
traceability
Can the system trace what changes propogated from Dev, to UAT to PROD. If it finds more than 50% change between Dev to UAT - that is acceptable; when it finds nearly 100% code similarty between UAT and PROD, it would be good to trace what changes finally moved from Dev to PROD.. Now we are adding this in the title.
7 votes -
Detect new databases and add automatically
We run 1 database per customer and are constantly adding databases, they follow a specific naming convention.
Having some way to auto add those databases to environments would help, or at a minimum alerting there are unmonitored databases on a server.
As an idea auto add based on
1) based on naming convention filters for database name
2) We would happily add a redgate table to our schema with an entry to specify environment etc for auto pickup
3) Schema is within X % of other databases of same type
37 votes -
JIRA plug-in support
Tie into Versions of a project inside JIRA to track an application through the life cycle.
21 votes -
Next/Previous Change button on drift page
Finding changes in long procedures is very difficult. Would be easier if at the top you had a Next/Previous change button which would scroll to where the changes are on the page.
7 votes -
Delete DDL trigger if script fails
If the database creation fails, the DDL trigger still gets created but fails when any schema changes are made. You can't rerun the installation script as the creation of a database fails, therefore the installation script should check for and delete the DLL trigger or if the script fails, the DDL trigger should be deleted/
6 votes -
Dashboard improvement
Can we have all the DATABASE SUMMARIZED VIEW shown on the dashboard without scrolling. Maybe do some re-positioning of the groups might work. THis will be useful at NOC where things are being monitored.
3 votes -
Notify me if the DDL trigger is deleted
If the DDL trigger is deleted or disabled the process stops notifying me of the change. I would expect that the dashboard would alert me that it is not monitoring the database - perhaps on a periodic basis - perhaps also offer me the option to check for drift on demand in that case?
5 votes -
Project Level Changes Notifications
We would like to see an email if something changed in the estate (as opposed to an email for each DB) We have 70+ dbs.. and when doing an upgrade an email suggested drift occurred would be more useful than 70 emails.
Also.. we were kind of hoping we could see given one database which ones match it... Or basically showing groupings by matching schemas... (This would help us keep an overall view)
1 vote -
Launch SQL Compare from the dashboard
I want to be able to launch SQL Compare to compare two different versions from within the dashboard
34 votes -
On demand checking instead of a DDL trigger
I don't want to put a DDL trigger on my database server. I want to have an 'update' button in the dashboard that lets me manually check specific database instances for changes.
30 votes
- Don't see your idea?