Updating to 2017

From Fishbowl
Jump to: navigation, search
MySQL.png
Fishbowl 2017.1 or higher uses an improved database technology. When updating from Fishbowl 2016.14 or earlier, the database will be migrated from Firebird to MySQL. This is a significant change that may require some extra time during this one-time update process. The following information may be helpful when migrating to MySQL.

General/Windows

  • MySQL will be installed automatically with the Windows Fishbowl installer.
  • The data migration tool will run when Fishbowl attempts to connect to a Firebird database.
  • The data migration tool can be run manually by opening Database Migration in the Fishbowl\server\bin folder.
    Data Migration.png
  • MySQL has different unique constraints than Firebird. For example, MySQL treats b201 and B201 as duplicates. In this case, the duplicates will be automatically renamed by adding the item ID to the end of the name. The migration tool logs changes in a text file so that the changes can be reviewed after the migration is complete.
  • A few columns in the database have been renamed which may require some minor tweaks to custom reports and queries.
  • Custom views will not migrate and need to be recreated after migration.
  • Fishbowl's MySQL install will be run on port 3305. Typically, MySQL defaults to port 3306.
  • If a customer needs a 32-bit server, they will need to manually install the MySQL server and connect Fishbowl to it.
  • The process for creating a new database is slightly different. Right-click the Fishbowl Server tray icon and select Options. Click the New Icon Button.png New button, enter a database name, and then click Connect. The checkbox to Include Demo Data will populate the new database with example data.
    New MySQL database.png
  • A new folder named Fishbowl MySQL will be created in C:\Program Files\Fishbowl MySQL. This folder should not be modified, moved, or deleted.
  • The database files are stored in C:\Program Files\Fishbowl MySQL\data
  • Unlike Firebird, there is no database file to copy. To move a database, a backup file must first be created. This can be done in the Small.Schedule.png Schedule module or by right-clicking the database name in the Fishbowl Server options. The .sql file created during the backup can then be restored on the Restore tab.
    MySQL backup.png
  • MySQL uses a .ini file to know where databases are located and for other settings. When Fishbowl installs MySQL, a my.ini file is included. When installing to a new location, that new my.ini file will be used and it will appear as though the database is lost. Follow the instructions below to connect to the existing database.
    1. In MySQL Workbench, right-click a connection and choose Edit Connection.
    2. Go to the System Profile tab and click the ... button next to the configuration file.
    3. Select the my.ini file from the previous install to find the existing database.

Mac

  • If the Fishbowl Server 2017.1 or higher is being installed for the first time on a Mac, MySQL will need to be configured by following the steps here. MySQL does not need to be installed if only the Fishbowl Client is being installed.
  • For users that are updating from Fishbowl 2016 to Fishbowl 2017, the Firebird database will need to be migrated by following the instructions here.

Linux

  • If the Fishbowl Server 2017.1 or higher is being installed for the first time on Linux, MySQL will need to be configured by following the steps here. MySQL does not need to be installed if only the Fishbowl Client is being installed.