Recorder 6 - Consortium

FAQ - Transfer to a New Server

Q. Transfer to a New Server

A. 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,, but these seem to be related to the setup of the network and not to R6.  Use the version which can be installed most easily on the operating system,  but note that a database can only be moved up two version. 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, 2014 or 2016,  and an SQL Server 2005 database can be moved to SQL Server 2008  or SQL Server 2012 but not to SQL Server 2014 or 2016 .  If this causes a problem the simplest thing to seek the help of a user with an appropriate intermediate version.   

1.    If you are not creating 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_data.mdf.

Users will not be able to use R6 until after step 6.

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 9).   

2. If you want to transfer map files then update your existing version of R6 to version 6.28 or above and take a security of the Map system. See documentation ‘Managing mapping system’ for details on how to do this.  If you don’t wish to keep the map files this isn’t necessary.

3.    Do a new network install on the new server using the latest install version . When doing 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. A guide to  installing on a Network  is available R6_Win10_1_64bit.pdf

4.    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.

5.    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.   

6.    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.)

7.  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 following SQL .

IF NOT EXISTS(SELECT * FROM Master.dbo.SysLogins WHERE Name='NBNUser')


EXEC sp_addsrvrolemember 'NBNUser', 'dbCreator'

EXEC sp_addsrvrolemember 'NBNUser', 'diskAdmin'





EXEC sp_addrolemember 'db_backupoperator', 'NBNUser'

EXEC sp_addrolemember 'db_datareader', 'NBNUser'

EXEC sp_addrolemember 'db_datawriter', 'NBNUser'

EXEC sp_addrolemember 'db_ddladmin', 'NBNUser'

EXEC sp_addrolemember 'db_owner', 'NBNUser'

EXEC sp_change_users_login 'Update_One', 'NBNUser', 'NBNUser'

9.  Transfer any files from the R6 User Files folder to the same folder on the new Server   

10.    Run the R6 upgrade to the latest version. 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 12.   

11.    On each workstation uninstall the workstation software  (via control panel) and run the install again pointing to the new server.

12. Map files can now be transferred. See Documentation  on Managing mapping system.