Server migration

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to 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.

  1. Migrate SIMS to the new SQL server
  2. Make copies of the PARS .mdf and .ldf files on your existing SQL server
  3. On the PARS IIS server, change the connect.ini for SIMS so it refers to the new SQL server
  4. Run a PARS version update on the PARS IIS server. You will need to enter the sa password for the new SQL server. This will create a blank PARS db on the new SQL server
  5. On the new server, find the location of the PARS db files by right clicking on the db then: properties > files > path column
  6. Stop SQL on the new server (in management studio, right click and Stop)
  7. Copy the files from #2 into the directory from #5
  8. Restart SQL (right click and Start)
  9. Run another PARS version update on the IIS server

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