Server migration

Jump to: navigation, search

Migrating the SIMS server (SQL)

If you are migrating SIMS to a new server this can refer to one or both of these jobs:

Transferring the SIMS SQL .mdf and .ldf files (i.e. the database files) to a new server.

The datatables that PARS uses are contained in the SIMS .mdf and .ldf files (there is no separate database), following the SIMS recommended procedures for relocating these files to a new SQL server will also transfer the PARS datatables. After reattaching the files to the new SQL server, make sure that SIMS .net workstation is functional on your PARS workstations (and PARS Connect IIS server if this is being used) and then run a PARS Service pack which will prompt you to enter the SQl SA password. No further work is required to get PARS up and running.

Transferring the contents of the shared SIMS folder to a new file server.

The SIMS file server hosts the shared SIMS folder. In many cases the s:\ is mapped to a shared network location containing the shared SIMS folder. Within this folder are various files important to PARS and PARS Connect. Transferring the contents of the shared SIMS folder (in particular SIMS\PARS) and ensuring your workstations have their SIMS.ini updated (if required) is all that is needed for PARS to remain functional.


If you previously used 'PUPIL SCAN' in PARS, you will be required to rebuild the Pupil scan database on your new SQL server as per the link below.

Migrating the PARS server (IIS)

To migrate PARS to a new server, simply follow the steps on the Installation page as if you were installing PARS from afresh. When you are ready, you can remove the old instance of PARS by:

  1. Stopping the PARS website in IIS Manager
  2. Stopping the PARSConnectKeepAlive process via Task Manager
  3. Removing the PARS website via IIS manager
  4. Deleting the PARS folder, usually found via C:\inetpub\wwwroot\PARS