Topic: Network - Transfer to New Server
These instructions apply to upgrading to v6.29 which is the last upgrade that can be run without being registered with the R6 Steering Group and having an update key for the current financial year.
Recorder 6 will install on any Windows operating system which can run SQL Server 2008, 2012, 2014 or 2016. A version with Management Studio must be installed. A few users on virtual servers have experienced problem, so avoid if you can. Use the version which can be installed most easily on the operating system, but note that a database can only be moved up two versions. For example a database on SQL Server 2000 (MSDE) can only be moved directly to SQL server 2005 or SQL Server 2008 and not to SQL Server 2012 or 2014, and an SQL Server 2005 database can be moved to SQL Server 2008 or SQL Server 2012 but not to SQL Server 2014. If this causes a problem the simplest thing is to seek the help of a user with an appropriate intermediate version. If you have R6 mapping that you wish to retain then you will need to update your existing system to V6.28 or 6.29 and do a Map System backup, which can be used to restore mapping . If you do not do this then recovery of the mapping data will be very difficult/impossible.
1. If you are not creating a new instance of SQL Server then you MUST make sure you have a backup of the R6 database. I would suggest that it is detached from the SQL Server instance and a copy made of NBNData.mdf.
Users will not be able to use R6 until after step 5. Make sure you have a copy of all the R6 user files including Map System backup if needed.
If you using a new instance of SQL server then this isn’t necessary. Users will able to use R6 until there workstation are updated (Step 8).
2. Do a new network install on the new server using install version 6.26 . See http://www.recorder6.info/page16.html. When doing the server software install you will be able to determine where on the new server the files go. Remember that users need to have SQL Server logins on SQL Server. More detailed information is available on the Recorder6,info site (see documentation) and a quick guide to installation is attached.
3. On a workstation which does not have Recorder installed (if you have one) run the workstation install. If you can’t use a new workstation then uninstall the workstation software on one machine (via control panel) and run the workstation install. It is worth making sure that all registry entries for R6 have been removed see https://forums.nbn.org.uk/viewtopic.php?id=7519
4. Check that everything is working. You will have an almost blank database at this time. It would be worth checking at this stage that normal users can use the system and not just administrators. Make sure that normal users can create new rucksacks, and do normal tasks in terms of adding records etc. Data added during this testing will be deleted at the next stage.
5. If you are still using the same SQL server instance, restore the original database taken in 1 above. If you are using a new SQL Server instance the detach the database from the original instance and attach it to the new instance. (See note at start about which version can be attached.)
6. When you move from one SQL Server instance to another the mapping of the database logins to the users can get disrupted creating orphaned users. Orphaned users in SQL Server occur when a database user is based on a login in the master database, but the login no longer exists in master. This can occur when the login is deleted, or when the database is moved to another server where the login does not exist. If this happens R6 will not be able to not open the database ( message will be something like EOleException: Cannot open database "NBNData" requested by the login). In this situation update NBNUser by running the SQL in the attached file.
7. Transfer any files from the R6 User Files folder to the same folder on the new Server .
8. Run the R6 upgrades to the latest version (see Recorder6.info). If you are on a version prior to 6.28 you will need to run the 6.28 upgrade, then the 6.29 uggrade. This will bring the database in line with the latest software and update the application software. Your test workstation should now be working properly. Other workstation will not be working correctly, so users should avoid using them for new data until after step 9.
9. On each workstation uninstall the workstation software (via control panel) and run the install again pointing to the new server. It is suggested that you check the registry and make sure that all the Workstation entries for R6 have been deleted.
10. If mapping is to be transferred refer to the instruction for Managing Mapping on how to restore on the new server from a backup.
Littlefield Consultancy - IT Consultants