1.0.1.1496 -  October 16th, 2014

New features

• Email notifications
  Users can now set up to receive emails when a database change is detected.
• Check for updates
  SQL Lighthouse will now notify the user when a new version is ready, and make it available for download.

Fixes and performance improvements

• This has been a great sprint for performance improvements, with both the web app and the back end being more responsive, and less intensive on servers SQL Lighthouse runs against.
• There are also a number of bug fixes, and we’d like to thank our alpha users for reporting them.

1.0.1.1394 - October 9th, 2014

The DDL trigger has changed in this release, so you need to reinstall the trigger using this script.

New features

• Audit history.
  On the Review changes page, as well as seeing which schema objects were changed, you can now see who made the changes, and download the SQL they ran.
• Further visual improvements
• Improved validation error messages

Fixes

• Fixed an issue where some types of schema change would stop the Review changes page loading
• SQL Lighthouse can now monitor databases with ampersands in their name

Limitations of audit feature

• Initially, audit won't appear on the Review changes page. It'll only appear for a particular database after you name/acknowledge changes on the review page for that database, or when a change is detected on that database.
• Audit doesn't work in these situations:
  •  Creating, dropping and editing schemas won't have an audit history (objects in a schema work, but not the schema itself).
  •  If a role is dropped, the audit history is shown next to the dropped role, but all the objects which have permissions on them for the role will be shown as edited, and no audit history for this action is shown on those edited objects (SC-7591).
  • If an object is dropped because the database itself is dropped, no audit history is shown for this action.
• Known issues:
  • Moving objects between schemas (ALTER SCHEMA … TRANSFER …) has always been shown as a drop and a create, but the audit history will only be shown for one of the drop and create events.
  • For large transactions, between 420 and 512 of the items in the transactions are shown, due to trigger rollover.
  • If there are lots of transactions, audit history will only be shown for 1024 of the transactions, due to RavenDB limitations.

1.0.1.1231 - October 1st, 2014

We've spent the last two weeks redoing SQL Lighthouse's user interface. We hope you like the new look! We'd love it if you installed this release and let us know what you think.

Changes include:

• Redesign of all pages, including the dashboard, configuration, and welcome pages
• On the dashboard, projects can be collapsed and filtered
• Projects have labels to show their status

1.0.1.1021 - September 24th, 2014

• Validation for connecting to SQL Servers, including credentials and server availability

1.0.1.927 - September 18th, 2014

The DDL trigger has changed again in this release: please reinstall the trigger using this script.

What’s new

• Some validation, and user-visible error messages, have been added to the config pages.
  This doesn’t include validation for passwords, but it’s something we’re planning to do. If there’s anything else you’d like to see here, let us know. 
• Transactional and snapshot replication problems with the DDL trigger have been fixed. It should now work with ANSI_PADDING set to off.
• The ravendb port has changed, because port 1337 is a commonly used port in development.
• Fixed a display issue with Firefox.

1.0.1.742 - September 10th, 2014

• Improved banner at the top of the page.
• Databases can now only be added once to an environment.
• The current version of SQL Lighthouse is now displayed.
• Extra logging for the web server.
• Several bug fixes. 

1.0.1.661 - September 3rd, 2014

1.0.1.602 - August 27th, 2014

• Based on your feedback, SQL Lighthouse now uses a database (RedGate) to keep track of schema changes, instead of tempdb.
• SQL Lighthouse is now compatible with SQL Servers where the transaction isolation level has been set to Snapshot.

Before you can use this new version, you need to run a SQL script on all the servers SQL Lighthouse monitors. You can download the script here. 

This script creates the new RedGate database, and replaces the old DDL trigger and stored procedures with new ones. It removes all the old SQL Lighthouse objects from tempdb. If you have any questions about the new objects, see The DDL trigger, or send us an email.

1.0.1.581 - August 20th, 2014

• Logging improvements
  We’ve added a lot more logging to SQL Lighthouse, to make it easier to resolve any problems. If you need to send us your log files, you can find them at C:\ProgramData\Red Gate\Logs\SQL Lighthouse
• Fix for the continuous loading bug
  In the previous release, some users found that SQL Lighthouse stayed on the loading page and never loaded properly. This should now be fixed.

If you install this release and do see the continuous loading bug, please contact us. If you could send us your logs (from C:\ProgramData\Red Gate\Logs\SQL Lighthouse), and tell us how many databases and environments you have set up, as well as any other information you think’s relevant, that’d be really useful. 

1.0.1.531 - August 13th, 2014

We've been a little quiet recently because of summer holidays and 'Down Tools Week' (where we work on new mini-projects for a week, a bit like Google's 20% time), but now we're back up to speed and the next alpha release is out. It includes:

• An improved configuration page
  You can now view and edit your configuration. We're planning to do more work on the configuration soon.
• Fixes for many bugs reported by our alpha users.

1.0.1.433 - July 16th, 2014

• Fixes an issue with the service where Null values in the RG_SQLLighthouse_v1 table cause the service to stop working.

1.0.1.419 - July 9th, 2014

• Improvements to the installer so that it now installs .NET 4.5.2 if it isn't installed already.
• Makes sure that all processes are disposed of as part of the services stopping.
• Display a loading message if the webserver is visited before the storage service has started.

1.0.1.382 - July 2nd, 2014

• Fixes the issue where asymmetric keys, certificates, symmetric keys, partition functions, partition schemes and tSQLt tests weren’t being ignored correctly.

1.0.1.351 - June 26th, 2014

Original release.