Procedure: Upgrade from SQL Express to SQL Standard or SQL Enterprise

This procedure is provided for informational purposes, a SQL Upgrade is not covered by FileHold support so if you wish support for this activity, this can be arranged for under a consulting project as a billable service.

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.

IMPORTANT:  backup all 5 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 SQLExpress to SQL Standard that the following occurs:

1) Stop the FHURM Service, FH Workflow Service, and WWW Service

  •  NOTE: When upgrading, to keep it simple, you can maintain the same SQLInstance name (this is an option) - if you want to change the instance name, then you will need to update all web.config's in FileHold in step 4.

2) 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 5 FileHold Databases, and has valid log in permissions in the SQL Management Studio.

OPTIONAL: if you need to change the DB Server instance name as part of the upgrade process, then you need to run the FHInstrumentation tool (using a Domain admin account logged into the FileHold server with access to the FH DB server)

  • Follow this procedure to launch the FHInstrumentation utility - then choose - Change DB Server instance - from the menu options. This will walk you through the changes.

www.filehold.com/help/system/fhinstrumentation-utility

3) START FileHold Services: After this, you can start up FHURM, FH Workflow 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.

4) 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.

http://www.filehold.com/help/technical/health-checker-tool

6) 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)

 7) Procedure Complete