This article describes how to perform a backup of the visitor id database, then restore the visitor id database on a different Microsoft SQL Server Instance.
Please note:
- You need visitor id v3.2.0.132 or higher to perform the below instructions. Please check your visitor id version and upgrade to the latest version if required.
- You will need basic skills in Microsoft SQL Server to complete the below instructions.
Instructions:
- Run visitor id.
- Click ‘File > Backup’.
- Choose ‘Database Only’.
- Click ‘Start’.
- Choose a backup location and click ‘Ok’.
- Once the backup is complete, locate the zip file that the backup created and copy this zip file to the new SQL Server.
- On the new SQL Server, unzip the backup zip file.
- Open SQL Server Management Studio and login.
- Expand the ‘Databases’ node and create a new database called ‘visitorid’.
- Expand the ‘Security > Logins’ nodes and create a new login using SQL Authentication.
- Restore the backup file to the newly created visitor id database.
- Create a new SQL Script and run the Stored Procedure ‘sp_changedbowner’ to set the newly created login as the owner of the newly created and restored visitor id database.
- Create a new SQL Script and run the Stored Procedure ‘sp_serveroption’ to set the SQL Server ‘Data Access’ setting to ‘True’. This is required for visitor id upgrades.
- Back in the visitor id software, click ‘File > Database Connection Parameters’.
- Click the ‘Change’ button.
- Read the warning and click the ‘Yes’ button.
- Enter the new SQL connection details in the ‘Database Connection Manager’ window.
- Click ‘Connect’.
visitor id should now be connecting to the new ‘visitorid’ database. If visitor id does not connect to the database then most likely the settings in the ‘Database Connection Manager’ window are incorrect. Please review these settings and if visitor id still does not connect to the new ‘visitorid’ database please contact the Future IT Support Team.
[helpful]