Database Merge Utility; Merge Utility Basics; Master Database - Inter-Tel AXXESS Manual

Hide thumbs Also See for AXXESS:
Table of Contents

Advertisement

5. DATABASE MERGE UTILITY

5.1
The Merge Utility is designed for sites that are converting a currently networked system
to an ATM System. Taking the information from existing nodes, this application merges multi-
ple databases into one file. This not only helps to maintain the integrity of the current informa-
tion, but it also eliminates the time-consuming task of having to manually retype entries.
NOTE:
first three digits. For example, 6.003 and 6.004 databases are both considered 6.00. Therefore,
if you have a 6.003 database, you don't need to convert it to a 6.004 database.
A. MERGE UTILITY BASICS
5.2
To successfully merge the databases, the Merge Utility uses the following four main
elements:
Master Database: Acts as the main file to which all databases are merged (see below).
Merged Database: Contains the information that is added to the master database (see
page
Merged Items: Consist of the specific items (e.g., devices and cabinets, extension IDs,
etc.) that can be merged (see
Merge Log: Logs any changes made and problems that occurred during the merge pro-
cess (see
5.3
Each of these elements is described in the following sections.

Master Database

5.4
To combine multiple databases, the Merge Utility uses an existing database and saves it
as a master database. Information from subsequent databases is then added to this master file
until all databases are merged. Although any number of databases can be merged, the master
data-base device limits are enforced for each device type. Because this application retrieves the
required information and copies it to the master database, existing databases are not deleted.
5.5
When selecting the master database, consider the following:
Using the system that is attached to the Voice Processing Unit as the master database
will speed up the merging process because all of the mailboxes and other associated
voice mail data will not need to be copied.
The programming for any devices or items NOT mentioned in this manual will remain
as originally programmed in the master database.
A v6.0 or later non-ATM database will be automatically converted to a v7.0 or later
ATM database.
The master must use one of the following number plans:

Database Merge Utility

INTER-TEL
When the Merge Utility compares the version of the merging databases, it uses the
6-24).
page
page
6-27).
Option 1: Consists of the following defaults:
Trunk Groups - 9201
Node Trunk Groups - 9501
Node Route Groups - 9701
Trunks - 94000
ARS - 9200
®
®
AXXESS
MANUAL VERSION 11.0 – May 2008
6-24).
Programming
Page 6-23
6

Advertisement

Table of Contents
loading

Table of Contents