This procedure is provided for informational purposes, a Microsoft SQL Server upgrade is not covered by FileCare. This can be arranged as a billable service.
Upgrading SQL for FileHold Software
Performing a SQL upgrade and the easy FileHold related steps below might be a 1 hour process, it depends on speed of server and how long the SQL upgrade takes.
Backup all FileHold Databases and Log files completely, ensure these backups are available by inspecting the backup files.
You will want to ensure before doing the upgrade of Microsoft SQL Express to SQL Standard that the following occurs:
- Stop the FHURM Service, FH Workflow Service, and WWW Service
- Perform the SQL Upgrade via the SQL installation process. This is not covered in this procedure. Reboot the server as required.
- Once complete - ensure that your FH_Service account is still the DBOwner of all FileHold databases, and has valid log in permissions in Microsoft SQL Management Studio.
- If you need to change the DB Server instance name as part of the upgrade process, use the utility in the FHInstrumentation tool.
- START FileHold Services.
- After this, you can start up FHURM (FileHold 15 and under), FH Workflow (FileHold 14 and under) and WWW Service. Usually after a SQL upgrade you need to reboot the server, so these services will start automatically if the Server reboot is performed.
- Run the Server Health Checker: Run the Health checker application to validate that all is functioning, by following this procedure page. Green/amber is good, red indicates a configuration issue.
- TEST THE SYSTEM. If all is green / yellow in the report, then you should login and test the FileHold system:
- add a document,
- search for a document,
- check out / check in a document,
- launch and complete a workflow (if you are using workflow)