Currently when I'm looking at the changes that have been made to a database I can only acknowledge the changes and give the new state a name, or leave the database as it is.

I want a button to rollback the changes changes on this database instance to the last known version.

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

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

As well as tracking the schema for changes I want to be able to track certain tables to see if the data changes too. For example configuration data

I would like to be able to select some of the changes listed and have a change report created like you can create in SQL Compare. I would then be able to save this report locally so that I can email it to my team to ask about the changes.

This is would be very helpful when team members are allowed to make changes to the dev schema, but don't always make the best design choices.

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

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.

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'd like to be able to acknowledge a state as being ok, without having to give it a name.

the ability to view all changes since a certain date would allow a DBA to migrate or roll back schema changes

show find change history of single objects, (who, when and what has changed on an explicit object.)

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!

Page automatically refreshes while reviewing schema changes and makes it difficult to review changes. Please include an option to disable refresh on the difference review pages, e.g.: localhost:19528/#/differences/DbObservations-483

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.

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.

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.

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

As some of the changes might be done by a procedure schedule through a SQL agent job, it would be very helpfull if a filter could be applied to ignore changes made by specific users.

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 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