Moving only the GoldMine database to a different SQL Server, how do we do this?
- Make sure that no one is actively working anymore within GoldMine, also not in any application with an integration to GoldMine like Microsoft Outlook or applications/services like GoldMine Web or using Synchronization.
1. Make a backup (.bak) of each database that needs to be moved to the new server within SQL Management Studio and provide it to the destination machine
- see generic instructions and recommendations for Microsoft SQL backups and restoring databases in the youtube video: Introduction to SQL Server Database Backup and Restore - YouTube
2. Take not yet off the original Microsoft SQL Server or the database(s)
3. Make sure that the new Microsoft SQL Server instance on the different server is installed correctly e.g. with Mixed Mode as described in the GoldMine Installation Guides, also make sure that Firewall rules are adjusted to allow incoming and outgoing connections, make sure that TCP/IP and Named Pipes protocols are enabled etc.
4. Restore the backup(s) within the SQL Server Management Studio on the new server,
- It is only possible to restore Microsoft SQL backups on the same or higher versions of Microsoft SQL, you cannot restore for example a Microsoft SQL 2016 database backup on a Microsoft SQL Server 2014 (the restore feature is not backward compatible)
- It is possible to restore database backups into different Microsoft SQL editions, for example, a Microsoft 2008 Standard Edition database backup can be restored into Microsoft SQL 2016 Express Edition if the limitations are not exceeded (database size less than 10 GB)
- It needs to be made sure that necessary SQL Logins which are used by GoldMine (DBALIAS.INI) are created and/or if applicable the Windows User (those who are using GoldMine) are added as Logins and appropriate rights (dbo) provided to the GoldMine database
- If the version of the Microsoft SQL server is newer than the original Microsoft SQL Server the database compatibility level of the restored database needs to be adjusted via Right Click on the Database >> Properties >> Page Options >> Compatibility Level (the value should always match the version of the Microsoft SQL Server version)
As it is recommended to use the identical Alias name for the restored database (otherwise Outlook link or integration settings need to be read on all machines again to refer to the new alias), it is necessary to make back-end changes to the DBALIAS.INI file
4. Browse to the GoldMine shared folder (where the LicenseGMxx.bin and the DBALIAS.INI resides)
5. Make a backup copy of the DBALIAS.INI
6. Open the DBALIAS.INI with an editor, this is only necessary for the main GoldMine database and the currently used Contact Set which in most cases is also the main GoldMine database - in the case also additional Contact set databases were moved, those additional database aliases should be solely adjusted from within the GoldMine application see step 17.
7. Change the HOST value in the specific ALIASx section
- If applicable but usually this will not change also adjust the DATABASE name)
- If applicable but usually this should be adjusted on the Microsoft SQL Server to have the same SQL username, also adjust the LOGIN
8. Save the DBALIAS.INI
9. Start GoldMine
10. There will be a message as a back-end change of the DBALIAS.INI is considered as a security breach and require to confirm the SQL Login credentials
11. Fill in the appropriate credentials and check the save password checkbox
12. Start GoldMine with master rights and verify the ALIAS entry again now from within GoldMine
13. Tools >> Databases >> Database Alias Manager
14. Highlight the specific adjusted Alias
15. Button Test Connection
17. If applicable and further contact set databases were also moved to the new Microsoft SQL Server
a. Highlight the specific Alias
b. Button Edit Alias
c. Adjust the Host information
d. If applicable also adjust the Database and Login information appropriately
e. Button Test Connection
19. Close GoldMine
20. Now turn off the original Microsoft SQL Server or archive/remove the original GoldMine database on the old Microsoft SQL server, so that they cannot be used anymore accidentally
21. Verify GoldMine still starts and works as expected and then let other users log in and also verify
- If using GoldMine Connect/GoldMine Web >> make sure to perform an IISRESET
- If clients have in their SQL connectivity (cliconfg on Windows 32-bit systems in C:\Windows\System32\cliconfg.exe on Windows 64-bit environments in C:\Windows\SysWOW64\cliconfg.exe certain Alias names defined they need to be adjusted for the new server.