Big Changes Coming for Lucity SQL Server Databases

Get prepared for a nice (but big) change coming for Lucity databases for our SQL Server clients. Historically, Lucity data has been spread across 10 databases (Comm, User, Work, Sewer, Storm, Street, Park, Water, Equip, and Electric). In Lucity 2015r2 (August 2015), a wizard will be provided to combine these databases into a single Lucity database. Data in a single database provides so many advantages for our clients including:

  • Simpler database backup and maintenance plans
  • Easier addition of new Lucity products
  • Better database file management
  • Improved cross database reporting
  • Streamlined database connection management

In addition to these advantages, it  allows us at Lucity to support new license models, add cool new features faster, and improve the overall stability of the software.

We are working hard to make the process of combining databases as easy and foolproof as we can. There will be a wizard provided which will walk through the process of pulling everything into a single database. It will automatically pull all of your Lucity tables, stored procedures, triggers, and data into the new database and will provide a comprehensive report of most custom objects in your databases. Custom objects must be manually transferred to the new database. This might include custom triggers, tables, views, security and schema, indexes, relationships, or stored procedures.

The process of combining databases can be done any time after upgrading to Lucity 2015r2 but must be done before upgrading to Lucity 2016 or higher. Oracle clients will not need to perform this process.

More information will be released in the next 3 to 4 months, in our release documentation for Lucity 2015r2, as well as at ACT in September.

Let us know if you have any questions or concerns, we are very interested in your feedback.

3 comments on “Big Changes Coming for Lucity SQL Server Databases

  1. Vince DiGirolamo says:

    Are the current table names, attributes, keys, triggers, constraints and/or indexes changing, or are they just being moved into a single database?

  2. […] this release also includes a tool to consolidate all of the numerous GBA* databases into a single new Lucity database. Stay tuned for some details on how this unification process works in the August edition of Looking […]

Leave a Reply to Vince DiGirolamo Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s