1 The installer updates the database
You do not run a query or a script on the database server to update SoftwareCentral.
The database is updated by the SoftwareCentral installer when you update SoftwareCentral. See Update SoftwareCentral and Updating the SoftwareCentral database.
2 Back up first
Take a backup before you start any update.
Before updating the database it is highly recommended to take a backup. If you do not take a backup of the database, you will be unable to roll back to the current version after the update.
3 If the installer cannot finish
Collect the details below and contact SoftwareCentral support. Do not change the database yourself.
- Check that the account the service runs under has read, write and execute permissions on the SoftwareCentral database (not needed for Azure SQL). See Prerequisites.
- Note the message the installer shows, and the database version from the message "The database is currently at version X.Y" if SoftwareCentral shows it.
- Note the version of SoftwareCentral you are installing.
- Contact SoftwareCentral support with these details.
4 Best practice
- Back up before every update. Without a backup you cannot roll back to the current version.
- Keep the database permissions. The service account needs read, write and execute permissions on the SoftwareCentral database (not Azure SQL).
- Write down the messages. The exact text of an installer or SoftwareCentral message helps support find the cause quickly.
- Check the version after the update. The "not up to date" message stops when the database and the program are at the same version. See Updating the SoftwareCentral database.
5 Troubleshooting
| Symptom | Cause | What to do |
|---|---|---|
| "The database is not up to date. The database is currently at version X.Y - Please update the database to version A.B" | The database is older than SoftwareCentral. | See Updating the SoftwareCentral database, then update SoftwareCentral. |