Administrator's Guide

6-9
Cisco Unified Attendant Console Administration and Installation Guide
OL-27293-02
Chapter 6 Configuring and Licensing Cisco Unified Attendant Console Advanced Server
Engineering Menu
Step 2 On a resilient system, you can test or repair the databases on either the Publisher or Subscriber server;
under Server Details, click the server as appropriate.
Step 3 In Server, type the name or IP address of the machine where the Microsoft SQL Server is installed. For
example, 209.165.202.128.
Step 4 Type your SQL Server Username. If Microsoft SQL Server was installed using the Cisco Unified
Attendant Console Advanced server Installation Wizard, the user name is sa.
Step 5 Type your Password. If Microsoft SQL Server was installed using the Cisco Unified Attendant Console
Advanced server Installation Wizard, the password is Z1ppyf0rever.
Note The SQL Server login password must be sufficiently complex to meet the Windows policy requirements
described at http://support.microsoft.com/kb/965823.
Step 6 If you have a non-resilient system, click Save, to save your new database selection.
Note There is no Save button in a resilient Cisco Unified Attendant Console Advanced Administration
installation.
Step 7 You are prompted that Cisco Unified Attendant Console Advanced server must be restarted for the
changes to take affect. Select the option to restart the server immediately.
Test the Database
To test the specified database, click Test Connection.
Repair the Database
To repair the specified database, click Repair Database.
Before repairing the database, Cisco Unified Attendant Console Advanced Administration must stop the
server. After the database is repaired you must manually restart the server service. If you have repaired
the database, you can view a repair report by clicking Database Repair Report. This opens a window
that displays the following information:
Database Name
SQL Server
Activity Start Date
Activity End Date
Status
Error Code
Error Description
Database Purge
The Database Purge option enables you to purge old call logging and operator session information from
the database. Customers using SQL Server Express may need to do this because their database size is
limited to 4 GB. If the logging database becomes full, some features and services may fail.