FAQs

How do you migrate your WinSPC database to different server software or hardware?

1. Backup the WinSPC database you want to migrate.


2. Using WinSPC's Installation and Configuration Guide, configure an empty database for WinSPC.  If you are moving to new server hardware, configure the empty database on the new hardware.  If you are not moving to new server hardware, configure the database on the current hardware. (The Installation and Configuration Guide can be found on your WinSPC installation CD or in the installation/upgrade files you downloaded from winspc.com. You can also get a copy of the guide by calling DataNet's Help Desk at 248-447-0140.)


3. From any WinSPC client station, launch WinSPC and log in as Admin.


4. Since a migration requires exclusive database access, force the logout of all stations currently connected to the WinSPC database. To do this:
   
   a. From WinSPC's Administrator window, click Tools > Force User Logout.
   
   b. In the Force User Logout dialog box that is displayed, multi-select all the stations listed.
   
   
   (Click to enlarge.) 
   
   c. Click the Logout button.
   
   d. Allow 30 seconds or so for the logout to be forced.
   
   e. Close the Force User Logout dialog box by clicking the Close button.


5. Launch the Migration Wizard by clicking Tools > Migrate from WinSPC's Administrator window.
   
   



6. Complete the Migration Wizard.  As you do, be aware that the prompts for database details pertain to the new, empty database configured in step 2 above. By the time the wizard completes, it will have:
   
   
   • Changed the DBState of the current database's Config table to 3, preventing future logins.
   
   
   
   • Tested the connection to the new database.
   
   
   
   • Created the WinSPC tables and fields in the new database.
   
   
   
   • Copied all appropriate data from the current database to the new database.
   
   
   
   • Updated the WinSPC.ini file in the shared folder used for WinSPC with the new database's login information. (The shared folder used for WinSPC refers to the shared folder that would have been created during the installation of WinSPC. The primary purpose of this folder is to facilitate the installation and configuration of WinSPC on client stations other than the first client station. It is sometimes referred to as the remote folder.) 
   
   
   
   Note: It may take longer than usual for a client to make its initial connection to a new WinSPC database following a migration. This is because it goes through the following process: attempts to connect to the former database; discovers that database is not available; goes to the shared folder for WinSPC; retrieves the path to the new database from that folder's WinSPC.ini file; updates its local WinSPC.ini file with that path; and connects to the new database.


7. If you want to move the shared folder used for WinSPC--a move that will be mandatory if the shared folder was on the same hardware as the former database and that hardware is no longer going to be accessible to WinSPC clients--complete the following steps:
   
   a. Have all client stations connect to the new database at least once. (If the shared folder is moved prior to a station connecting to the new database, the station will have no way of detecting the path to the new database as explained in the step 6 note above.)
   
   b. Copy the shared folder to the desired location, ensuring this location is accessible by all WinSPC clients. (If you don't know the current location of the shared folder, open any WinSPC station's local WinSPC.ini file and locate the line that begins ImageDir=. The path that follows ImageDir= is the location of the shared folder. The default installation location for a local WinSPC.ini file is C:\> Program Files > DQS > WinSPC.)
   
   c. Share the newly copied folder as required.
   
   d. Edit the newly copied folder's WinSPC.ini file to reflect the new location of the shared folder. To do this, change the path on the line in the file that begins ImageDir= to the path of the new location.
   
   e. For any client station that will access the shared folder using a mapped drive, map a drive to the folder in its new location.
   
   f. For any client station that will access the shared folder using a UNC path, change the ImageDir= path in the station's local WinSPC.ini file to reflect the new location of the shared folder.