Updating databases in

04 Mar

For more information about major version upgrades, see the documentation for your DB engine listed following.Minor version upgrades usually contain database changes that are backward-compatible with the previous version of the database.One of the smart features of Database Manager is that database configurations for the most popular public databases are updated automatically, by downloading configuration data from the Matrix Science web site.This means that, for databases such as Swiss Prot and NCBIprot, all you need do to make a new sequence database available for searching in Mascot is: When a new database is created, unless it is predefined, you will either need to supply download URLs for the files or copy the files manually to the specified directory on the Mascot Server before configuration can be completed.The following terms may benefit from additional explanation: Database Name: Each database must have a unique name. Note that these names are case sensitive, and much confusion can be caused by creating both Swiss Prot and swissprot.Local paths: The delimiters between directories must always be forward slashes, even if Mascot is running on a Windows system.This will cause an SQL error in some database engines.

One of the main principles of SQL databases is the schema: a formal declaration of how the database is organized.Major version upgrades can contain database changes that are not backward-compatible with previous versions of the database.This functionality can cause your existing applications to stop working correctly.As a result, Amazon RDS doesn't apply major version upgrades automatically; you must modify your DB instance manually to perform a major version upgrade.You should thoroughly test any upgrade to verify that your applications work correctly before applying the upgrade to your production DB instances.