Create message databases 

Overview

In addition to the procedures that follow, you should read the Message Care readme.txt file that is delivered with the software. The readme.txt file includes late-breaking changes to and news about the software.

This section provides instructions on how to create message-related databases. The messaging software requires the following three databases:

The MCAdmin database is typically quite small in size; however, the MCMessages and the MCArchive databases can grow quite large over time. We recommend that you choose a large logical hard drive exclusively for carrying the message databases. The sum of all the database capacities (as specified by the maximum file size parameter you will enter during the database creation process) should not exceed the size of the logical drive minus any space already taken.

Before you create the message databases, determine the appropriate sizes for each database, particularly the MCMessages database (holds all email messages).

Database size is restricted by the following:

Create MCAdmin database

To create the MCAdmin database, do the following:

  1. From the Start button, select Programs->Microsoft SQL Server 7.0 (or Microsoft SQL Server)->Enterprise Manager.

  2. Expand the Microsoft SQLServer->SQL Server Group, and then locate and expand the SQL Server machine name. Right click on the Databases folder, and then select the New Database item to bring up the Database Properties dialog box.

  3. From the General tab, enter the name of the new database you want to create in the Name text box. In this case, the database name is MCAdmin.

  4. Take note of the default location of the database in the Location field (in SQL Server 2000, the file property information is located on the Data Files tab). Change this field to the desired location, if necessary.

  5. In the Database files group, type 1 in the Initial size (MB) field.

  6. In the File properties group, do the following in the order shown:

    • Leave the Automatically grow file box checked.

    • In the File growth-> By Percent option, accept the default 10 percent.

    • Select the Maximum file size-> Restrict filegrowth (MB) option, and then type 200 for the file size.

  7. Select the Transaction Log tab.

  8. Take note of the default location of the transaction log file for this database in the Location field. Change this to the desired location.

  9. In the Transaction log files group, type 1 in the Initial size (MB) field.

  10. In the File properties group, do the following in the order shown:

    • Leave the Automatically grow file box checked.

    • In the File growth-> By Percent option, accept the default 10 percent.

    • Select the Maximum file size-> Restrict filegrowth (MB) option, and then type 20 for the file size.

    • Select the OK button.

  11. Expand the Databases folder and locate the newly created MCAdmin database.

  12. To open the MCAdmin Properties dialog box, right-click the MCAdmin database, and then select the Properties item.

  13. Select the Options tab.

  14. From the Settings group, select the Auto shrink check box and leave the defaults (Auto create statistics , Torn Page Detections, and Auto update statistics) checked.

  15. Select the OK button.

Create MCMessages database

To create the MCMessages database, do the following:

  1. From the Start button, select Programs->Microsoft SQL Server 7.0 (or Microsoft SQL Server)->Enterprise Manager.

  2. Expand the Microsoft SQL Server->SQL Server Group, and then locate and expand your SQL Server machine name. Right-click the Databases folder, and then select the New Databases item to bring up the Database Properties dialog box.

  3. From the General tab, enter the name of the new database you want to create in the Name text box. In this case, the database name is MCMessages.

  4. If the default location of the database in the Location field is not correct, then change this field to the desired location (in SQL Server 2000, the file property information is located on the Data Files tab) Change this field to the desired location, if necessary.

  5. In the Database files group, type 100 in the Initial size (MB) field.

  6. In the File properties group, do the following in the order shown:

    • Leave the Automatically grow file box checked.

    • In the File growth-> In megabytes option, type an appropriate incremental number of MB to which you want your database to grow. Ensure that the incremental File growth value is an integral multiple factor of the Restrict filegrowth value plus the Initial size value and that the value for the database capacity in msgcare.ini file is also an integral multiple factor of the Restrict filegrowth value plus the Initial size.

      For example, if the Initial size value is 100 MB, the Restrict filegrowth value is 2000 MB, and the database capacity in msgcare.ini file is 1800 (90% of 2000), then 50MB could be used as the incremental growth size. That is the database can grow by increments of 50MB to eventually meet the 2000 MB limit.

      For example: (38x50) + 100 = 2000

      • 2000 = the Restrict filegrowth value

      • 100 = the Initial size of the database

      • 50 = the incremental growth size

      • 38 = integral multiple factor

      For example, (34x50) + 100 = 1800

      • 1800 = the maximum database size specified in msgcare.ini file

      • 100 = the Initial size of the database

      • 50 = the incremental growth size

      • 34 = integral multiple factor

      If however, you use an incremental growth size that is not an integral multiple factor of the Restrict filegrowth value plus the Initial size (for example, 400), the MCMessage database would eventually grow to 1700 (100->500->900->1300->1700) and then SQL would stop growing the database because the next increment would be 2100 (greater than the Maximum file size). The messaging software on the other hand would continue to poll and process new message calls after the database grew to 1700 because you set a value of 1800 in the msgcare.ini file.

    • Select the Maximum file size-> Restrict filegrowth (MB) option, and then type the number of MB to which you want to restrict the file growth.

  7. Select the Transaction Log tab.

  8. Take note of the default location of the transaction log file for this database in the Location field. Change this to the desired location.

  9. In the Transaction log files group, enter 10 in the Initial size (MB) field.

  10. In the File properties group, do the following in the order shown:

    • Leave the Automatically grow file box checked.

    • In the File growth-> In megabytes option, enter 10.

    • Select the Maximum file size-> Restrict filegrowth (MB) option, and then type 300 for the file size.

    • Click the OK button.

  11. Expand the Databases folder, and locate the newly created MCMessages database.

  12. To open the MCMessages Properties dialog box, right-click the MCMessages database, and then select the Properties item.

  13. Select the Options tab.

  14. From the Settings group, select the Auto shrink check box, and leave the defaults (Auto create statistics , Torn Page Detections, and Auto update statistics) checked.

  15. Select the OK button

Create MCArchive database

To create the MCArchive database, do the following:

  1. From the Start button, select Programs->Microsoft SQL Server 7.0 (or Microsoft SQL Server)->Enterprise Manager.

  2. Expand the Microsoft SQLServer->SQL Server Group and then locate and expand your SQL Server machine name. Right click on the Databases folder, and then select the New Databases item to bring up the Database Properties dialog box.

  3. From the General tab, enter the name of the new database you want to create in the Name text box. In this case, the database name is MCArchive.

  4. Take note of the default location of the database in the Location field (in SQL Server 2000, the file property information is located on the Data Files tab). Change this field to the desired location, if necessary.

  5. In the Database files group, type 5 in the Initial size (MB) field.

  6. Accept the defaults in the File properties group.

  7. Select the Transaction Log tab.

  8. Take note of the default location of the transaction log file for this database in the Location field. Change this field to the desired location.

  9. Accept the defaults in the File properties group. Select the OK button.

  10. Expand the Databases folder and locate the newly created MCArchive database.

  11. To open the MCArchive Properties dialog box, right-click the MCArchive database, and then select the Properties item.

  12. Select the Options tab.

  13. From the Settings group, select the Auto shrink check box and leave the defaults (Auto create statistics , Torn Page Detections, and Auto update statistics) checked.

  14. Select the OK button.

Modify the MCMessages capacity

Important!

The messaging software is designed to handle database capacity conditions. As the capacity of the database is reaching its maximum, the messaging software will generate alarms. The messaging software generates alarms at 80%, 90%, and 95% of the database's capacity.

After you have created the message databases, you need to modify the MCMessages database capacity in the msgcare.ini file located in the Message Care server Winnt directory. The messaging software uses the value in the Maximum Database Size (MB) parameter to issue warning messages when the MCMessages database grows close to this limit and stops processing any new incoming message calls when this limit is reached. Some additional space (10% or so) should be left in the actual database allocation to allow for additional database operations.

To modify the capacity of the MCMessages database, do the following:

  1. From the Winnt directory on the Message Care server, locate the msgcare.ini file.

  2. Locate the Maximum Database Size (MB) parameter.

  3. Set the value for the Maximum Database Size (MB) parameter to 90% of the maximum file size you administered in SQL for the MCMessages database.

    Specifically, 90% of the value you entered in the Select the Maximum file size-> Restrict filegrowth (MB) option in the General tab.

    For example, if you entered 2000 in the Restrict filegrowth option, then 1800 (90% of 2000) should be the value you specify in the Maximum Database Size (MB) parameter.

   


Copyright © 2001
Avaya Inc.
All rights reserved.
Modified: March 19, 2001