Dedicated Server Notes
Your private dedicated server uses MariaDB as its SQL engine (with various enhancements added, like AppSynergy's Federated features).
MariaDB is largely compatible with MySQL so most tools that support MySQL will generally work with MariaDB.
This includes MySQL GUI and command line tools for various operating systems including Windows.
To learn more about connecting to your dedicated server, see the
Database API documentation.
Manual Schema Changes
If you create or modify database schema outside of the AppSynergy user interface, beware of the following:
- When AppSynergy creates or modifies tables it also maintains a variety of extended meta data that is critical to
the proper operation. You will see a set of meta data tables named parasql_* in your database.
These should never be modified except by AppSynergy or by special instructions provided by AppSynergy support.
- If you issue CREATE TABLE commands directly to the database (instead of via the AppSynergy UI) AppSynergy's extended
meta data will not be created; this limits AppSynergy functionality with these tables. You can, however, manually
add the extended meta data with special instructions provided by AppSynergy support if needed.
- If you issue ALTER TABLE commands directly to the database (instead of via the AppSynergy UI) AppSynergy's extended
meta data will not be updated. Further, your application's references to table names, column names, data types, etc.
will not be updated. This may result in applications with broken references. Issuing an ALTER TABLE command
only for the purpose of adding a column or a unique index is safe so long as no existing column definitions are changed.
- AppSynergy linked user accounts: You should never change the password for any AppSynergy linked user account.
This includes root@localhost, root@%, u####@%, and db#####public@% user accounts.
Also, you should never change permissions on any AppSynergy linked user account except via the AppSynergy UI
(AppSynergy uses extended meta data to manage roles). Never create your own database user accounts directly; always
use the AppSynergy UI. If you need to create additional database user accounts for
other software to access the database directly, you should do so by creating an API Key via Tools > API Keys... so
that the security permissions for that user can be managed via the AppSynergy UI.
Database Backup via Command Line Tools
AppSynergy automatically performs nightly backups of your entire database server. You can also create a backup at any time
on demand to your own local computer.
Note that in the example below the options --master-data --single-transaction acquire a global read lock on
all tables at the beginning of the dump for only a short period of time. This allows a dump to run against a
live database and still deliver a consistent snapshot without blocking reads and write.
Recommended way to create a local backup of your database:
mysqldump --host=dbs-myserver.parasql.com --user=root --password=mypass --triggers --routines --events --master-data --single-transaction db11234 > mybackup.sql
Connecting To Your Database via MySQL Workbench
NOTE: AppSynergy has an integrated SQL Console which eliminates much of the need for MySQL Workbench.
See Tools > SQL Console... for details.
You can connect directly to your AppSynergy database with MySQL Workbench.
Workbench allows you to issue any SQL command as root, which has slightly more permissions than a AppSynergy Administrator.
The gsutil Command Line Utility
To copy files to or from your bucket you will need gsutil. The gsutil program is a free Google utility.
You can download it here.
When you configure gsutil be sure you are logged in with the same Google account you used to create
your AppSynergy account (we can add additional users to your bucket upon request).
When gsutil config asks you for a project id, please specify: parasql-app
Example: copy a local file to your AppSynergy cloud bucket using gsutil:
gsutil cp MyLocalFile.sql gs://db11345.storage.parasql.com/dumps/loadme.sql