Guest

Cisco Remote Monitoring Suite Option

Alarms Database Maintenance (Release 4.6)

  • Viewing Options

  • PDF (96.3 KB)
  • Feedback
Alarms Database Maintenance

Table Of Contents

Alarms Database Maintenance

Overview

Re-Indexing the Alarms Database

Creating and Cloning Databases

Manually Creating Databases

SQL Server Security


Alarms Database Maintenance


Overview

For the most part, the Alarms Database is set up to take care of itself. Database options are set so that its transaction log file is automatically truncated and shrunk. In addition, database statistics are updated at LGMapper/LGArchiver startup, and the database is completely re-indexed once per week during a restart. To perform other maintenance operations, you use SQL Server Enterprise Manager or other techniques.


Note The process of completely re-indexing the database is time-consuming. For a 1 GByte database, re-indexing can take up to 10 minutes, for smaller databases the time required to re-index is less as the re-indexing time requirement is proportional to the size of the database. Re-indexing is done once per week at the most, and occurs when the server restarts.


Re-Indexing the Alarms Database

If you want to manually re-index the database, you can use the stored procedure reindex_database to do this.

Creating and Cloning Databases

The LGCnfg tool is used to create new Alarms databases and to clone existing databases. Additional information on how to do this is included in in Creating a New Database and Cloning a Database.

Manually Creating Databases

To assist you in creating a databases manually, we provide SQL scripts in the DBScripts folder created during the installation process.

If you manually create a new database, you can initialize the database with the proper set of tables, data, and stored procedures by running the batch file InitDatabase.bat.

The InitDatabase.bat file takes a single command line argument using the name of the database to populate. Keep in mind that this batch file does not create the SQL Server database for you. You must first create the SQL database by other means.

As an example, if you created an empty database called LGMapper_Test, you could populate it with the following command run from the DBScripts folder:

InitDatabase LGMapper_Test

Once the database is created and populated, you make LGMapper use it by running the LGMapperCnfg tool and selecting it in the Alarms Database tab.


Note The preferred method of creating new databases is to use the LGCnfg tool as described in Creating a New Database and Cloning a Database.


SQL Server Security

During installation, the installer creates three local user groups:

LGM Readers

LGM Users

LGM Administrators

These groups are added to the Login collection in the Security folder seen in the SQL Server Enterprise Manager. In addition, these groups are added as users to the three (3) databases created during the installation process. The LGM Readers and LGM Users groups are given the db_datareader role for these databases so that they can perform queries against the databases, and the LGM Administrators group is given the db_owner role for these databases.

If you create new databases using either LGCnfg or the SQL scripts provided, these groups are added to the database Users as part of the creation process.

If you want to give a user access to AlarmTracker, all you need to do is add the user to the appropriate LGM XXX group.