1. Chris Wright Senior Systems Engineer, Lucity MOVING TO ONE DATABASE FOR SQL SERVER

2. OVERVIEW In 15R2 the customer has the option of utilizing either the individual Lucity databases (GBAComm, GBASewer, etc) or migrate to a single, unified database (Lucity). Prior to upgrading to version 16 or beyond, the databases must be unified, therefore, all clients MUST upgrade to 15R2 A wizard is provided in Client Maintenance to assist with the transition

3. NO NEED TO UNIFY RIGHT AWAY

4. WHY A SINGLE DATABASE (LUCITY) New licensing models Faster development times (less complexity) Conforming database model for Oracle and SQL Server Fewer database objects (fewer Views and redundant Tables) Easier file management (only one database file) Easier to support

5. WHY A SINGLE DATABASE (YOU) Simpler database backup and maintenance plans Easier to add new products. Only requires a new license file Simpler database connections for customizations Easier to Support The migration may reveal problematic database modifications

6. WIZARD Once upgraded to 15R2, a Unify button will be available in Client Maintenance What does it do? Restore a Lucity unified database to your instance of SQL Server Restrict access to the existing GBA* databases Transfer data from the GBA* databases to the Unified database List Custom Objects on your GBA* databases Update configuration information to point to the unified Lucity database

7. CONSIDERATIONS Recommended to perform the Unification process at a separate time after upgrading Custom objects (any database object not included out-of-the box) must be manually transferred after the Unification process Review your Custom objects and processes to see if they are still relevant and if they will need to be modified to account for the unified Lucity database After running the Unification Wizard it will be necessary to re-install any Web Products and run the Lucity.CreateDSN.exe tool on your workstation and services install Elevated permissions are needed to run the Unification Wizard successfully

8. CUSTOM OBJECTS & PROCESSES The View Custom Objects report in Client Maintenance will only show Objects (tables, indexes, views, stored procedures, triggers, users, etc) that reside within the GBA* databases Other Objects or Processes not detected that may need to be modified: Database Backup Processes SQL Server Jobs and Maintenance Plans Custom Programs that connect to the database Views in 3 rd Party databases that reference Lucity databases

9. MIGRATING PROCESS Fully upgrade to 15R2 Review the Custom Objects report for each installed client from Client Maintenance Investigate any Custom Objects listed and determine if they should be included in the Unified Lucity database and if they need to be modified in any way. Script out the objects as appropriate. Investigate if you have any Custom processes that reference the individual GBA* database and determine what steps will need to be taken after the Unification process (Database backups, integrations, maintenance plans, etc) Watch the YouTube demo of the Unification Wizard (September version of Looking into Lucity or via the 2015r2 Release Announcement in the Support Center)

10. MIGRATING PROCESS Test, if possible. Use a Test environment or run through the Wizard (Skip the Lock Down step and at the end of the Wizard select the option indicating you were just performing a trial run) Schedule a date to perform the migration Run Client Maintenance and run the Unification Wizard (the Unify button) Move your Custom Objects to the Unified Lucity database Modify any Custom Processes to reference the Lucity database Reinstall Lucity Web Products and run the Lucity.CreateDSN.exe on your Services and Workstation installs