There are times when due to unspecified data anomalies the current GoldMine database may need to be "rehosted" to a new GoldMine database. The GoldMine Support Desk or a GoldMine Solutions Partner may ask this process to be carried out. This process should not be carried out unless there is a specific need or request from the GoldMine Support Desk or a GoldMine Solutions Partner.
WARNING: If moving from and older version of GoldMine (pre 9.0) You will need to verify you don't have any custom fields that may be using any of the SQL protected words or characters.
The field name should not contain spaces or special characters, such as asterisks (*), an underscore(_) immediately following the U, apostrophe's ( ' ) or percent signs (%).
Do not use any of the following SQL reserved words as field names: UNION, UNIQUE, UNPIVOT, UPDATE, UPDATETEXT, USE, USER.
If these filed names are imported into SQL could result in data loss and duplicate records.
1 - Please have all users exit GoldMine.
2 - Make new SQL backup(s) of the GoldMine SQL database(s).
3 - Login to GoldMine as a user with MASTER rights.
4 - Click Tools >> Databases >> New Database. The Rehost GoldMine database wizard will appear.
5 - Select both options for "Create or copy data for contact set tables" and "Create or copy data for base GoldMine tables" >> click "Next".
6 - Click the "Alias Manager" button. The Database Alias Manager will appear.
7 - In the Alias Manager click the "New Alias" button.
8 - Provide an "Alias Name" similar to but not the same as the existing live database, ensure the "Host" is the name of the machine hosting SQL including named instance if applicable, key the SQL "SA" account credentials >> Click "Create New Database" button.
9 - There will be a message confirming "Database created successfully." >> Click OK then OK two more times.
10 - In the Rehost Wizard select the newly created database for the contact set tables and GoldMine tables as well as provide a "friendly" description of the new database >> click "Next".
11 - On the next screen under "Select source of data for the new database" select "Copy data from the currently active database" >> click "Next".
12 - Provide a Contact set code that does NOT match an existing database >> click "Next".
13 - Click Finish; at this point GoldMine will copy existing data showing progress through several database tables, this process can range from a few seconds to a few hours depending on the size of the database.
14 - If there are any errors please capture the full error message and as much detail as possible such as the date and time of the error and Contact GoldMine Support or GoldMine Solutions Partner.
15 - Once the process is finished GoldMine will state that the data has been successfully hosted and would you like to use the new MSSQL database as the default database; please select "Yes". At this time GoldMine will close and you will be presented with a GoldMine login screen, please login as the MASTER user again.
16 - Verify you are connected to the new rehosted database by clicking Help >> About GoldMine >> and then the "System" button. The entries for "GoldMine Files" and "Contact Files" should read as the newly rehosted database name for both entries.
17 - Test the result of the problem behavior. NOTE: If using Universal Search or testing the Universal Search function it will take time to allow the SQL Full Text search indices to re-populate; depending on database size this will take minutes to hours.
18 - If rehosting the database fixed the issue then either use this new database as the permanent default database or take a new backup and restore over the original database in SQL Server Management Studio.
NOTE: If there are undocked machines in use their file code must be updated to match the rehosted database code but the database name does not need to match on the undocked machines. to change this on the undocked machines click Tools >> Databases >> Open database >> Highlight the database >> click "Properties" button >> update the file code >> click "OK"