ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon 2019 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Documentation & Release Information
DrillDown Icon Known Issues (non-release related)
DrillDown Icon Configuration Information
DrillDown Icon modusGate & modusMail
DrillDown Icon modusGate Only
DrillDown Icon modusMail Only
DrillDown Icon SQL Server Information
DrillDown Icon How-To: Enable Full Text Indexing for SQL Server Express
DrillDown Icon Known Issue: SQL Server Express Setup Problems on Windows 2000 Server
DrillDown Icon Info: Extended Database Format for ModusMail
DrillDown Icon How-To: Configure the SieveStore Database in SQL Server
DrillDown Icon How-To: Use SQL Server Instead of the Built-in MDB Database for Quarantine storage
DrillDown Icon How-to: Prevent Quarantine-Related Problems
DrillDown Icon How-To: Configure SQL TCP stack
DrillDown Icon How-To: Move SQL database from one server to another
DrillDown Icon MySQL Information
DrillDown Icon Security
DrillDown Icon Sieve
DrillDown Icon Spam and False-Positives
DrillDown Icon Statistics and Monitoring Section
DrillDown Icon Web Components
DrillDown Icon Troubleshooting
DrillDown Icon Hardware & OS System Requirements
DrillDown Icon Tools
DrillDown Icon Other Product Technical Information
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
 
How-To: Use SQL Server Instead of the Built-in MDB Database for Quarantine storage


Product:
ModusMail

Version & Build: 4.1.361 + up



This how-to explains how you can set-up ModusMail or ModusGate to use MS-SQL 7 or MS-SQL 2000 database instead of the built-in Access/Jet-based database to improve the Quarantine performance.
 

There are 3 steps to this process:

1) Create the necessary tables in MS-SQL;
2) Create a system DSN on the machine running modus;
3) Point the modus Quarantine to the new database.


Step #1 - Create the necessary tables in MS-SQL

First, create the tables that Modus needs to store the Quarantine info in MS-SQL. 

Please use the script available in ...\Vircom\ModusMial\DBStructures to automatically create a new database with the tables included.  See New SQL 2000 script for Quarantine Database for details.

 

Open the SQL Script with Notepad:
a) Click on START;
b) Click on Programs -> Microsoft SQL Server -> Enterprise Manager;
c) Click on Tools -> SQL Query Analyzer;
d) Select the SQL server hosting the database you wish to use;
e) Cut and Paste the script to the Query Analyzer window (see screenshot);


f) Execute the script;
g)The script might generate two errors because it will try to delete existing tables of the same name
   (tblMsgCatalog and tblRecepients), ignore those messages;
h) Using SQL Enterprise Manager, browse the database in question and check to see if tblMsgCatalog
   and tblRecepients were created;
i) Note that when you create the system DSN on the next step, it must be an account defined in the SQL security,
   not an NT account. For instance, the default "SA" account would do fine;
j) Ensure that the specified SQL Account has enough rights to read/write information from/to tables
   ("tblMsgCatalog","tblRecipients"), used by the Quarantine mail store.


Step #2 - Create a system DSN on the machine running modus
 
a) Go to START -> Settings -> Control Panel -> Administrative Tools;
b) Double click on Datasources (ODBC);
c) Select System DSN and Put in a Datasource Name;
d) If the SQL server is installed on remote computers the authentication method should be
   "With SQL Server authentication using a login and password entered by the user".
   You cannot use Windows NT authentication with a remote SQL Server
   because the local SYSTEM account has no network credentials;
e) Put in the usual datasource username & password and click on Next;
f) Change the default database to the one containing the two datastore tables we created in step one
   and continue to click on next until you get to test the datasource. Make sure the test is successful.
 

Step #3 - Point the modus Quarantine to the new database

a) Go to the modus console -> system -> Quarantine database tab;
b) Type in the datasource name, username and password and hit apply;
c) At this point, modus should be able to talk to the MS-SQL server for it's Quarantine datastore.

 

 

Step #4 - Restart the MODUSCAN and MODUSADM services to force modus to use the new ODBC Driver

 
Modified 1/11/2007
Keywords:
Article ID: 1324