Moving a GoldMine Database to a New SQL Server
This article originally appeared on MCB Systems' Blog.
We wrote down a few notes while moving GoldMine databases from a SQL 2012 Express instance on one server to a SQL 2016 Standard instance on another server. This is not a detailed procedure, but if you are familiar with SQL and GoldMine, you may find it useful. We’re currently using GoldMine 2017.1.0.377.
Big Tip: Move one database at a time while you are still logged in to another database on the old server. You can only edit database aliases while logged in to GoldMine, and you can only log in to GoldMine if you can open a database. So open a dummy database and work on your other databases.
- In GoldMine, open a dummy or test database (create one if necessary) on your old server. These databases should include contact set tables and base GoldMine tables. (Tools > Databases > Open Databases or New Database)
- Use SQL Management Studio to detach one of your main databases from the old server and attach it to the new SQL server. In the database’s Security > Users section, make sure you see the SQL user that GoldMine uses (e.g. “goldmine”). Add that user if it’s missing.
- Back in GoldMine, go to Tools > Databases > Alias Manager. Edit the alias for the database you just moved. You should only have to change the host. Test the connection and make sure to set up the SQL Browser and firewall rules.
- Repeat steps 2 and 3 for any other databases you have.
- Finally, in GoldMine, open one of your main databases, then repeat steps 2 and 3 to move your dummy/test database.
Should you have any questions related to this article, don't hesitate to contact us.