Moving an Address Book To Another SQL Server

Steps to move your Maximizer Address Book from one SQL Server to another would depend on the version of Maximizer you are currently using.

Maximizer CRM Enterprise 2020 or later

When moving a Maximizer database from one SQL server to another, and after restoring the database and connecting it to Maximizer, it is necessary to map the maximizer_system SQL login from the SQL server to the Maximizer Address Book as the maximizer_system user with the dbo database role.

Before you begin, please do not delete the Maximizer database you intend to move from the list of available databases until this whole operation is complete. If you do this too early, you will lose the original passwords of its database users and will have to reset them.

Steps:

1. On the original server, use the SQL Server Management Studio to back up the database you intend to move.
2. Copy the backup to the new SQL server.
3. On the new server, open SQL Server Management Studio and restore the backup.
4. Expand the restored database and select Security Users.

• You will see a maximizer_system user already on this database.

1. Delete the maximizer_system user. If you get an error, do the following:
   1. Expand down to the now-restored database and click on Storage > Full-Text catalogs.
   2. For each catalog shown, right-click on each and choose Properties.
   3. Under General, change Owner from maximizer_system to dbo.
   4. Once done for all full-text catalogs, try deleting the user again. It should succeed.
2. Open Properties for maximizer_system SQL login.
3. Select the User mapping page.
4. Map the maximizer_system login to the Address Book with dbo role.
5. If you have not already done so, you need to add the old SQL server as a linked server (ref: Create linked servers - SQL Server | Microsoft Docs).
6. Run the following SQL query against the new SQL server's MaConfig database to migrate the ability to login with old passwords onto the new SQL server, replacing with the name of the new SQL server, with the name of the old SQL server and replacing with the SQL database you are migrating:

   
   INSERT INTO Login_Identity(UserID,[Database],[Server],Salt,[Hash],[Version],[Flags],LastPasswordChange) SELECT UserID,[Database],'',Salt,[Hash],[Version],[Flags],LastPasswordChange FROM [].Maconfig.[dbo].Login_Identity WHERE [Database] = ''

   
   Chage the [] (in FROM []) to the instance name of your old SQL Server.

1. Now you must employ this database in the new Maximizer CRM Enterprise 2020 (or later) environment using the following steps:
   1. Launch the Maximizer CRM Windows Administrator module on the Maximizer CRM Application Server.
   2. If prompted to log in click Cancel.
   3. Click File New Address Book…
   4. Change the Database Server to the new SQL Server if need be. Click Next.
   5. Log in with your SQL server SQL Authentication credentials and click OK.
   6. Change Target Action to Employ an existing Maximizer database.
   7. From the Database name dropdown, choose the database you are migrating and click Next.
   8. Click Start.
   9. When the employing the database is complete, click Close.
   10. Click OK after the MASTER password has been set to CONTROL.
   11. When you get control back again, click File Open Address Book…
   12. Select the database you just employed and click Open.
   13. Type in the MASTER password, which now is CONTROL, and click OK.
   You can now login to Web Access to this migrated database as the MASTER user with the password CONTROL. When you do this the first time, you will be prompted to change it. Make a new password.
   Other users should now be able to login to the new server with their current passwords.

The following section is DEPRECATED. Maximizer CRM version 2020 and newer have switched authentication models to Single Sign-On using SAML2 and have switched security models to a token-based method using OAuth.