Summary:

Here are the series of steps to change the MMSMail database name, and update related jobs and services so that they will function properly.

Detailed Information:

Login to SQL Query Analyzer as sa, and execute the following statements:

--------------
use master
go
EXEC sp_renamedb 'oldname', 'newname'
go
--------------

You will also need to update:

1. Registry settings for the EMF services.
2. The EMF Resin.conf file.
3. The SQL jobs installed by EMF: Cleanup Tables, Create Summary Tables, Queue Aging Actions, Queue Thresholds. Some installations of EMF may also have installed the jobs Backup MMS Database and Trash Queues Cleanup.
4. Webadmin SQL login accounts.
5. Any other SQL jobs implemented by a local DBA.

Resolution:

1. You will need to modify a registry key for each EMFservice:

HKLM \ Software \ TUMBLEWEED \ MMS \ folder for each 'service configuration'

The Configuration catalog key must be changed to reflect the new name of database.

2. Open the file:

Tumbleweed \ Email Firewall \ Resin \ resin.conf

with a text editor. Find the WebAdmin section, and alter the line including the string 'mms.default.catalog' to read the value as the name of the database. Save changes.

3. Each SQL job installed by EMF references the MMSMail database after installation. If you change the MMSMail database name, you need to update each SQL job with the new database name. This can be done from within SQL Enterprise Manager. Right-click job name > Properties > Steps, and double-click each step name. Select the new database name in the Database field (if there is a Database field; some steps will not have a Database field).

Also check the Command subwindow in each step. Most steps will reference a stored procedure, i.e., mmsSp..., but any explicit references to the database name in any step must be changed. Simply replace the old name by typing the new name over it.

Click Apply and OK to save the changes.

4. Once you renamed the database, all the WebAdmin SQL login accounts that were previously added to that database will no longer be associated to it. What this means is that the WebAdmin user will not be able to log in to the new database. You probably have to execute sp_dropuser and sp_droplogin stored procedures to clean up some leftovers, then use sp_adduser and sp_addlogin to re-add the login account.

5. If the SQL Administrator has created a SQL Database Maintenance Plan (Schedule Backup/DBCC) against the old MMSMail database, they might need to re-create them.