asked on September 24, 2015
...except that it does and seems to work fine.
Hello all,
A customer wants to change the database name. When testing, we discovered the although the renamed database seems to work completely fine (existing site info was read and new licenses were assigned), LFDS posts a lot of errors (every 6 seconds roughly) about being unable to connect to the old database name.
I noticed the db_settings table has the old database name stored in the legacyName row.
So I have two questions:
- Can the legacyName field be updated to the new database name? If I update the table will I break anything? If so, I'll recommend creating the database from scratch or going back to the old name.
- Just for interest, why does the LFDS database need to store it's original name?
-Ben
0
0