Information you will need
- From the old SQL Server:
- Application-specific login name and password (typically 'TksGuard1PlusUser')
- Master database name
- Configuration database name
- The names of all mounted Archive databases
- For Guard1 Plus SE :
- The username and password for an application Supervisor account
- For the new SQL Server:
- Server name or IP and instance name if applicable
- Report Server name or IP address
- Report Server Virtual Directory name
- Inform end users that the system will be offline.
- User can continue to download PIPEs to IP Downloaders during the outage - the IP Downloaders will store the data until the system is back online.
- USB Downloaders should be unplugged until the migration is complete. Ensure that all USB Downloaders are disconnected before proceeding - this ensures that PIPE data will not be downloaded inadvertently to the old database.
- On the application server where Guard1 Plus SE Server is installed, disable the TKS Guard1Plus Attendant Service. This will prevent IP Downloaders from communicating with the system and inadvertently downloading data to the old database.
- On the old SQL Server:
- Back up the Guard1 Plus SE Master database (typically 'Guard1Plus') as a BAK file.
- The Configuration database (typically 'Guard1PlusConfig') does not need to be migrated except when you have a large number of application users. Application user accounts are stored in the Configuration database - if you do not migrate it you will have to set those accounts up from scratch. If you wish to migrate the Configuration database:
- In SQL Management Studio, expand the Guard1PlusConfig database folder (your Configuration database may have a different name).
- Expand the Tables folder.
- Right-click dbo.DataSource and select Edit top ### rows
- In the query pane, select each populated row, right-click and select Delete. These rows will be recreated by the Data Maintenance Application later in the procedure.
- Back up the Configuration database as a BAK file.
- Back up all mounted Archive databases as BAK files.
- Copy the resultant BAK files to a flash drive or network folder accessible from the new SQL Server.
On the new SQL Server:
- Verify that SQL Server is set to use Mixed Mode (Windows and SQL Server) Authentication. Guard1 Plus SE is not compatible with Windows Only authentication mode.
- Verify that the SQL default collation method is set to SQL_Latin1_General_CP1_CI_AS. Guard1 Plus SE requires a case-insensitive collation method.
- Using the BAK file created in Step 3-a, restore the Master database, overwriting the new empty Master database created in Step 5-l.
- If applicable, use the BAK file created in Step 3-b-v to restore the Configuration database, overwriting the new empty Configuration database created in Step 5-i.
- If applicable, use the BAK file(s) created in Step 3-c to restore all Archive databases as new databases.
- Review the Security > Users folder for each restored database and delete the stale application-specific SQL login if applicable.
- In the Security> Logins folder, double-click the application-specific Login (usually TksGuard1PlusUser) to open its Properties dialog.
- In the left pane, click User Mapping.
- In the right pane, check the Map box next to each database, then highlight each database and check the db_owner box in the role membership pane. When all databases have been mapped to the login, click OK.
- On the application server where Guard1 Plus SE Server is installed:
- Log in to Windows as a Local Administrator.
- Run the Data Maintenance Application from Start > Programs > TimeKeeping Systems.
- Log in with Supervisor credentials.
- Click Advanced > Change SQL Server.
- Check both of the Change the connection parameters... boxes and click OK.
- Specify the name or IP address of the new SQL Server (or select it from the dropdown list).
- If you are using a Named Instance, include the instance name after the server name (e.g. ServerName\InstanceName or 192.168.1.1.\InstanceName)
- Specify a Windows or SQL login with SYSADMIN privileges on the new SQL Server (e.g. SA).
- Click Next.
- Enter the name of the new Configuration database that will be created on the new SQL Server (default is 'Guard1PlusConfig').
- Enter the name and password for the application-specific SQL Login that Guard1 Plus SE will use to connect to SQL Server and the Guard1 Plus SE databases. This Login will be created on the new SQL Server if it does not already exist.
- Click Next.
- Enter the name of the new Master database that will be created on the new SQL Server (default is 'Guard1Plus').
- Click Next.
- Specify the name or IP address of the Reporting Services Server, the name of the Report Server Virtual Directory (normally 'ReportServer'), and the desired name for the Guard1 Plus SE reports folder (default is 'G1PSE').
- If using SSL on the Report Server, check the Use SSL (HTTPS) box.
- Click Finish.
- Exit the Data Maintenance Application.
- Launch Guard1 Plus SE. It should open without error.
Mounting Archive Databases
To mount the Archive databases you restored in the previous procedure you will need the Archive database names as displayed in SQL Server Management Studio.
On the application server where Guard1 Plus SE Server is installed:
- Run the Data Maintenance Application and log in with Supervisor credentials.
- Click Mount Archive.
- In the Archive Database Name field, enter the name of the first Archive database.
- Click OK. The Archive will be added to the Databases list.
- Repeat this process for remaining Archive databases.
Once all Archive databases are mounted, they will be available in the File > Open Archive list in Guard1 Plus SE Client.