"The ease of use and implementation were key to our decision to move ahead with FileHold."
- Engineering Customer
Change Database Instance
This utility updates all web.config's if you need to move the databases and log files to a different server or server\instance.
Please follow this procedure precisely - you must be an IT administrator with SQL administration and domain administration membership that is a member of the local Administrators group on the FileHold Server.
If your log files are large, don't forget that you need to do full backups of log files and shrink the log files. Check your SQL documentation for information on Management\maintenance plans.
- Ensure that on new MS SQL Server that you are running a supported version, and that the FH_Service has security login permissions set in the SQL Management Studio.
- The FH_Service account must be a domain account, and must have the necessary permissions.
- Please check the Server Preparation Guide for more details, this is included with the Server Installation Kit.
- Ensure all users are logged off from FileHold
- Stop FH App Pool in IIS Admin
- Backup all 5 x FileHold Databases - they begin with CH_ - make sure you choose verify in SQL Management Studio.
- Verify these backups exist by finding them in the backup location designated.
-
Stop Services
- Stop FHURM Instance service in the services control panel
- Stop FileHold Workflow Instance (if running, this is an optional feature of FileHold and may be disabled, if so - ignore this step)
- Stop WWW Services
- Detach all 5 Databases from the SQL Management Studio
-
Copy all 5 Databases and Log Files to the new server
- (WARNING: DO NOT MOVE THESE FILES, USE COPY to AVOID Windows Explorer losing these files)
-
Attach all 5 databases and log files in the new Server's SQL Management Studio
- Confirm that the domain\FH_Service account is still the DB Owner of all 5 databases.
Start up FileHold
- Start FHURM Service
- Start FH Workflow Service (if you use Workflow optional feature)
- Start WWW Service
- Start FH App Pool in IIS Admin 7.X
- Run the Health Checker
If the health checker is all green and yellow, then proceed to testing
- Login to FileHold
- Add a document
- Search for a document
- Check out and Check in a document
- Launch and Complete a Workflow (if using this)
Ensure that the Databases, Database Log Files, and the FileHoldData storage path which includes, Document Repository, FullTextSearch and FHURMObjects, are all properly backed up, since the Databases and log files are now in a new location.
1 week later, you can remove the Databases and log files from the old server, or at any time you can copy these to an backup system and remove them from the old Database server.
You should also consider uninstalling MS SQL Server on the old server.

