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.

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.

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/

The dev database is going to be drifting frequently, and we don't need an email every time that happens. But we definitely want to know when prod is changed. We would like to turn on notifications per environment, or per database.
We may also want one person notified if Project A changes, and another notified about Project B.

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.

Setting up IIS Application routing to resolve to http://localhost:19528 when requesting http://lighthouse.dev.local, causes the application to generate a 400 error - The request hostname is invalid.

This should also propagate to the links generated in the email notifications

It would be really nice if Lighthouse had the ability to push change notification to external systems, e.g. Slack.
This could either be acomplished with a http post functionality, or with a general powershell script support.

Tie into Versions of a project inside JIRA to track an application through the life cycle.

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.

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)

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

While viewing the differences, it would be valuable to be able to expand\collapse the changes so devs can see a list of changes, then expand to see what those changes were...

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.

The biggest PITA of all in RedGate Source Control is everyone having to each configure each database. It would be WONDERFUL if those configuration settings for Source Control could be set in the SAME database as SQL Lighthouse so that not everyone needs to configure them!

Why are there limitations on number of projects? We have dozens!!!

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?

We have several Azure SQL Databases. It would be great to be able to monitor those too.

This is great! When will I be able to do this with Oracle databases?

I don't want to have to keep naming the states of my databases. It should automatically use the revision numbers from my version control system

I want to check that our dev server is in sync with version control. I want to show the head of my version control system as an environment, so I can see it side by side