Moving PremiSys Databases onto a new SQL server

Updated 7 months ago by Marty

Moving PremiSys Databases onto a new SQL server

Two instruction sets are explained in this article to move a SQL database

1. Performing a SQL backup to be restored onto the new SQL Server.
2. Detaching the SQL databases from the old SQL server, then copying and attaching the databases on the new SQL Server.

*Please read the entire procedure before you begin. If you have any questions, consult your SQL Admin or call PremiSys Tech Support.

NOTE: Microsoft SQL Server Management Studio will be needed to move the databases

Performing a SQL backup to be restored onto the new SQL Server

1. 1. Log into the current SQL instance using SQL Server Management Studio with either the sa account login or an account that has sa rights.
2. Expand the database folder showing the available SQL databases.
3. Right click on the Premisys Database and hover over the tasks option.
4. This will open the tasks menu where you will see the backup option, select it.
5. Click OK to run the Backup.
6. A successful message will appear as shown below, click ok.
7. Repeat steps 3-6 for the Cardholders database.

NOTE: Unless the path has been changed the backups will be located in the at the location below saved as premisys.bak and cardholders.bak.

C:\Program Files\Microsoft SQL Server\MSSQL10_50.IDENTICARD\MSSQL\Backup

Restoring SQL Backups of the Databases onto the new SQL Server

1. Copy the backed up database files to the desired new location. (The new path must be local to the new SQL service.)
2. Connect to the current SQL instance using either the sa account login or an account that has sa rights.
3. Right click on the Databases folder and select Restore Database.
4. Select from Device and browse to the square control with three dots.
5. Click the Add button to browse to the Premisys backup file.
6. Click Ok, Ok, and Ok again to start the restore.
7. Once the restore is complete repeat steps 3-5 for the Cardholders backup file.
8. You will need the appropriate ChangeApplicationOwnedTablestoDBO.sql. For this, contact your certified Premisys integrator.
9. In SQL Management Studio click File > Open > File and browse to the file you saved above. You may have to re-enter your SQL credentials.
10. Toward the end of the script you need to type in the name of the computer running the "IDenticard Windows Service" service and the name of the IIS server.
11. Click the Execute button to run the script. If you see any errors below in red, run it a second time. If it runs without errors, the databases are good
12. Now you will need to update the localConfigV2.config file on the Server and any connected client.
13. Open the C:\Program Files\IDenticard\LocalConfigV2.config file in Notepad. You will need to change three lines in this file: SystemDB_Server, CardholdersDB_Server, and LookupDB_Server. (See highlighted below  on where to make the changes.
    1. <LocalConfig>
       <ArrayOfEntry>
       <add key="CardholdersDB_Server" value="PCName\Instance"/>
       <add key="CardholdersDB_Database" value="Cardholders"/>
       <add key="CardholdersDB_UserName" value="pDfmqf2QeGLorbWLKor1mw=="/>
       <add key="CardholdersDB_Password" value="qnkBzJDgADBCnuR83Z/U5hHqiq
       +YKr+r9t5TqWq9iWw="/>
       <add key="SystemDB_Server" value=" PCName\Instance "/>
       <add key="SystemDB_Database" value="PremiSys"/>
       <add key="SystemDB_UserName" value="pDfmqf2QeGLorbWLKor1mw=="/>
       <add key="SystemDB_Password" value="qnkBzJDgADBCnuR83Z/U5hHqiq+YKr
       +r9t5TqWq9iWw="/>
       <add key="LookupDB_Server" value=" PCName\Instance "/>
       <add key="LookupDB_Database" value="PremiSys"/>
       <add key="LookupDB_UserName" value="pDfmqf2QeGLorbWLKor1mw=="/>
       <add key="LookupDB_Password" value="qnkBzJDgADBCnuR83Z/U5hHqiq
       +YKr+r9t5TqWq9iWw="/>
       <add key="CheckLicensing" value="false"/>
       <add key="RememberUsername" value="true"/>
       <add key="LaunchProductionUI" value="true"/>
       <add key="ServerOnly_ServicesServerHost" value="AppServerName"/>
       <add key="DatabaseReadConfigValueRetries" value="3"/>
       
14. Save the file and restart the Identicard Windows Service. Once the service is started log into Premisys. The data is now connected to new SQL server instance.
15. The easy way to update the client PCs is to take the updated config file from the server and copy it to all the client machines.

NOTE: The following only needs to be done on a Premisys System not PremisyID

The last step is to change two text files in the Inetpub folder on the IIS server (usually the same PC as the service server). The first is located at C:\Inetpub\wwwroot

\IDenticard\web.config, and you need to edit the DB server name on the same three lines, almost exactly like you would in the LocalConfig file. The second file is located at C:\Inetpub\wwwroot\IDenticard\Services\web.config and needs pretty much the same edit.

Detaching and Moving Databases to a New SQL Server Location

1. Log into Microsoft SQL Server Management Studio.
2. Expand the SQL Server and the databases.
3. Right click on the Premisys Database and select tasks, then select detach.
4. Repeat step 4 for the Cardholders database.
5. Browse to C:\Programs Files\Microsoft SQL Server\MSSQL12IDenticard\MSSQL\DATA folder where you will find the 4 files you need; premisys.mdf, premisys_log.ldf, cardholders.mdf, and cardholder_log.ldf.
6. Copy those 4 files and move them to the new PC that is going to house the SQL Server.
7. On the new PC log into Microsoft SQL Server Management Studio.
8. Right click on the databases folder and select Attach.
9. Click the add button and browse to the location of those 4 files and select the Premisys.mdf file then click Ok.
10. Repeat steps 9-10 for the Cardholders Database.

How did we do?

Related Articles

• Moving PremiSys ID Databases onto a new SQL server
• SQL Server Database Requirements
• Installing PremiSys to an Existing SQL Server.