Expanding an ICM SQL Database

Similar documents
ICM Logger Database Configuration Synchronization

Tune the CTC HEAP Variables on the PC to Improve CTC Performance

UCS Uplink Ethernet Connection Configuration Example

CRS Historical Reports Schedule and Session Establishment

Lab - Manage Virtual Memory in Windows 7 and Vista

SQL Server 2000 Setup Configuration for ICM 5.0

CallManager Configuration Requirements for IPCC

Cisco Aironet Client Adapter Installation Tips for Windows NT v4.0

CTC Fails to Start on Windows XP with Cisco Security Agent

WebView and IIS Connection Timeouts

Configuring Funk RADIUS to Authenticate Cisco Wireless Clients With LEAP

How to Change the IP Address of One or More Cisco ICM NT Servers

Reestablishing a Broken Cisco CallManager Cluster SQL Subscription with CallManager 3.0, 3.1 and 3.2

Syslog Server Configuration on Wireless LAN Controllers (WLCs)

Cisco Unified CCE Data Server

Use NAT to Hide the Real IP Address of CTC to Establish a Session with ONS 15454

World Wide Web Service Crashes on WebView

Viewing and Troubleshooting Perfmon Logs

Configure BIOS Policy for Cisco UCS

Lab - Configure Browser Settings in Windows 8

Manage and Generate Reports

Cisco Secure Desktop (CSD) on IOS Configuration Example using SDM

Core Component Installation

Preupgrade. Preupgrade overview

NAT Support for Multiple Pools Using Route Maps

LepideAuditor for File Server. Installation and Configuration Guide

Using a Virtual Machine for Cisco IPICS on a Cisco UCS C-Series Server

Avaya Definity G3 Skill Group to Service Mapping and Extension Configuration

Upgrade BIOS on Cisco UCS Server Blade

Database Administration

Database Administration

CDR Database Copy or Migration to Another Server

Fixing Issues with Corporate Directory Lookup from the Cisco IP Phone

Troubleshoot Missing Speed Dials Issue in IPMA

Configuring the VPN Client 3.x to Get a Digital Certificate

Lab B: Configuring Disk Compression and Quotas

Technical Brief Exporting a List of Device MAC Addresses from Xcalibur Global Document Version 1.0

Reestablishing a Broken CallManager Cluster SQL Subscription with Cisco CallManager

Cisco Unified IP Phone 7942/7945/7962/7965/7975 Firmware Upgrade from pre 8.3(3) to 9.3(1)

Database Administration

IP Phone 7940/7960 Fails to BootProtocol Application Invalid

EMC Ionix ControlCenter (formerly EMC ControlCenter) 6.0 StorageScope

ASA Clientless SSL VPN (WebVPN) Troubleshooting Tech Note

Personal vdisk Implementation Guide. Worldwide Technical Readiness

AS Series Media Processor: Apple Segmenter HTTP Handler Setup

Hotdial on IP Phones with CallManager Configuration Example

Optional Lab. Identifying the Requirements. Configuring Windows 7 with virtualization. Installing Windows Server 2008 on a virtual machine

NTP Software File Auditor for Hitachi

Configuring the Cisco VPN 3000 Concentrator with MS RADIUS

Configuring and Using Redundant Disks with Cisco MCS

Storing Your Exercise Files

CajunRules Policy Manager for Solaris Getting Started Guide Version 2.0

Version 6.3 Upgrade Guide

MySQL On Crux Part II The GUI Client

The system is temporarily unable to complete your call. Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: 10045

Oracle Call Center Connectors

Data Center Network Manager (DCNM) with SFTP Switch Configuration Backup

Novell ZENworks Asset Management 7

Enabling the Catalyst Web Interface on Catalyst 4500/4000 Series Switches Running CatOS

MDCStoreTools Data Management Utility

KG-TOWER Software Download and Installation Instructions

Configuring the NetBackup Cloud Connector for use with StorReduce (v1.2)

Administrator s Guide

Microsoft Word - Templates

DefendX Software Control-Audit for Hitachi Installation Guide

KYOCERA Net Admin Installation Guide

Windows 2000 Disk Management

Migrating from Connect To Image Center 2.0

UCCE WebView Frequently Asked Questions

Workspace Administrator Help File

Guidelines for Using MySQL with Double-Take

ACS 5.x: LDAP Server Configuration Example

Strategic Reporting Systems, Inc.

NETWRIX PASSWORD EXPIRATION NOTIFIER

Client Installation Guide

NTP Software Defendex (formerly known as NTP Software File Auditor) for NetApp

Lab - Create a Partition in Windows 8

Integration of Customer Instance with Shared Management

Preparing to Use Click to Call

Installation Guide. . All right reserved. For more information about Specops Deploy and other Specops products, visit

Step by Step SQL Server Alerts and Operator Notifications

Lasso Continuous Data Protection Lasso CDP Client Guide August 2005, Version Lasso CDP Client Guide Page 1 of All Rights Reserved.

CONFIGURING TARGET ENVIRONMENT FOR AUDIT BY NETWRIX WINDOWS SERVER CHANGE REPORTER TECHNICAL ARTICLE

Installation Guide Install Guide Centre Park Drive Publication Date: Feb 11, 2010

PEAP under Unified Wireless Networks with ACS 5.1 and Windows 2003 Server

UCSM Faults Report and SNMP Traps

Print Manager Plus 2010 Workgroup Print Tracking and Control

Cisco Secure ACS for Windows v3.2 With PEAP MS CHAPv2 Machine Authentication

Auxiliary Port, Console Port, and Adapter Pinouts for Cisco 1000, 1600, 2500, 2600, and 3600 Series Routers

Jonas Activity Management Technical Deployment Guide

Common Ground Upgrade

Monitoring Inventory. Inventory Management. This chapter includes the following sections:

Installing GFI MailArchiver

MeetingPlace for Outlook Onsite Installation or Upgrade


Print Station. Point-and-Click Printing WHITE PAPER

XLmanage Version 2.4. Installation Guide. ClearCube Technology, Inc.

Client Installation and User's Guide

PST for Outlook Admin Guide

Acronis Backup & Recovery 11 Beta Advanced Editions

Transcription:

Expanding an ICM SQL Database Document ID: 20493 Contents Introduction Prerequisites Requirements Components Used Conventions The Basics Expand Space with Use of ICMDBA When To Use Enterprise Manager Expand Space with Use of SQL Enterprise Manager SQL Server 6.5 SQL Server 7.0 and SQL Server 2000 Related Information Introduction This document describes how to expand a Cisco Intelligent Contact Management (ICM) database to give the database more room for data or log space. Prerequisites Requirements Cisco recommends that you have knowledge of these topics: ICM databases Cisco Intelligent Contact Management Database Administrator (ICMDBA) utilities Microsoft Structured Query Language (SQL) database sizing concepts Components Used The information in this document is based on these software and hardware versions: ICM version 4.6.2 and later SQL Server version 7.0 The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions.

The Basics There are three types of databases that you might need to expand: Logger Administrative Workstation (AW) Historical Database Server (HDS) All three are expanded in the same way. ICM provides a utility that you can use to manipulate databases, ICMDBA. ICM version 4.6.2 supports both SQL Server 6.5 and 7.0. ICM versions 5.0 and later support SQL Server 2000. You can also use the Microsoft utility called Enterprise Manager. Either method results in an expanded database. In SQL Server 6.5, databases are made up of one or more logical devices. In SQL Server 7.0, databases are made up of one or more physical files. Each device or file is assigned a specific role, such as data or log space. When multiple devices or files are used for a single database, they do not have to be in the same location. This is convenient when you expand a database because it allows you to put the new device or file on a different logical and/or physical drive. When you expand a database, you can either expand an existing device or file, or create a new device or file. Either way, the database has new space available. When you expand a database, the goal is to give the database more room for either data space or log space. Both can be expanded in the same way. Expand Space with Use of ICMDBA When you use ICMDBA to expand a database, the utility automatically creates device or file structures as needed. Note: Shut down services for ICM during the expansion. Complete these steps in order to run ICMDBA and expand the database: 1. Run the ICMDBA.EXE command to launch the utility. 2. Find the machine, instance, and database you want to expand. 3. Right click the database, and choose Expand. Figure 1 Properties

4. The Expand dialog box opens. Check either Data or Log under Component in order to choose the type of expansion. Figure 2 Expand 5. Choose the location of the expansion drive under Available Drives. 6. Enter the amount of additional space (MB) in the Expansion Size field. 7. Click OK. 8. Choose Server > Start from the menu bar in Figure 1. When To Use Enterprise Manager While it is easier to use ICMDBA to expand databases, it is necessary to use Enterprise Manager if either of these is true: You must leave ICM services running. You are expanding the database dramatically (15 GB or more).

Note: For SQL Server 6.5, a single device should not have more than 16 GB of space. Use multiple devices if you have a database larger than 16 GB. The procedure for multiple devices is similar to the Expand Space with Use of ICMDBA procedure. The only difference is that you repeat the steps for each 15 GB device you need to create. This limitation does not exist for SQL Server 7.0 or SQL Server 2000. Expand Space with Use of SQL Enterprise Manager SQL Server 6.5 Complete these steps in order to expand a device that exists: 1. Double click the device, or right click the device and choose Edit from the pop up menu in order to modify. Figure 3 SQL Enterprise Manager The Edit Database Device dialog box opens. 2. Increase the size (MB) value to the new size, and click Change Now. Note: Enterprise Manager limits the size (MB) value to the available drive space, so the value cannot be set to exceed the available drive space. Figure 4 Edit Database Device

Complete these steps in order to create a new device: 1. Right click the Database Devices folder, and choose New Device from the pop up menu. The New Database Device dialog box opens. 2. Assign a Name, Location and Size (MB) for the new device, and click Create Now. Figure 5 New Database Device

Other than the assign a name and location step, the procedures on how to expand a device and create a device are the same. The expansion of a device that exists is a very clean expansion because no new devices are created. However, it limits you to the amount of space available on the drive where the device is located. Therefore, you cannot take advantage of space available on another drive. Nevertheless, it can be a good option if drive that exists has plenty of space available. Complete these steps in order to expand space when you use a device that exists: 1. Launch the SQL Enterprise Manager. 2. Expand the server in the Server Manager window. Note: Register the server, if the server is not already registered. 3. Expand the Database Devices section. 4. Find the device you want to expand and right click the device name. 5. Choose Edit from the pop up menu. 6. Change the size to the new size (for example, from 500 MB to 1000 MB). 7. Click Change Now. Now that the device is expanded or a new device is created, expand the database itself. Complete these steps: 1. Expand the Databases section in the Server Manager window. 2. Right click the database to be expanded. 3. Choose Edit from the pop up menu. The Edit Database dialog box opens. Figure 6 Edit Database

4. Click Expand. The Expand Database dialog box opens. Figure 7 Expand Database 5. Choose the device you just expanded or created in the appropriate menu (Data Device or Log Device).

6. Enter the amount of new space you wish to expand for this database in the Size (MB) field. Note: Most likely, all of the available space is used. 7. Click Expand Now. SQL Server 7.0 and SQL Server 2000 Complete these steps in order to expand a database that exists from the Console Tree: 1. Navigate to the Databases folder for your server. 2. Double click the database, or right click the database and choose Properties from the pop up menu in order to modify. Figure 8 Console Root The Properties dialog box for the selected database opens. 3. Click the General tab to increase the size of the data files for the database, or click the Transaction Logs tab to expand the size of the transaction log files for the database. 4. Adjust the Space Allocated, as needed, and click Apply to commit the changes. Figure 9 Properties

Note: ICM version 4.6.2 and earlier do NOT support the Automatic File Growth feature of SQL Server 7.0. This feature should be disabled for both data and transaction log files. Uncheck the Automatically grow file check box to disable this feature. If there is insufficient disk space to expand existing data and transaction log files, a new disk drive can be added to the server, and new data or transaction log files can be created for the selected database on the new disk drive. Complete these steps in order to create a new data or transaction log file: 1. Click the appropriate tab in the Properties dialog box. 2. Click the blank line under the file listings that exist, and enter the File name, Location, and Space Allocated (MB) for the new file. 3. Click Apply to commit the changes. Other than the assign a file name and location step, the procedures on how to expand a file and create a new file are the same. Complete these steps in order to expand space when you use data or a transaction log file that exist: 1. Launch the SQL Enterprise Manager. 2. Navigate to the Databases folder for your server in the Console Tree. Note: Register the server, if the server is not already registered. 3. Right click the database you want to expand. 4. Choose Properties from the pop up menu. 5. Click either the General tab to expand a data file, or click the Transaction Log tab to expand a transaction log file. 6. Adjust the Space Allocated (MB) setting to the new size (for example, from 500 MB to 1000 MB).

7. Click Apply to commit the changes. Related Information Technical Support & Documentation Cisco Systems Contacts & Feedback Help Site Map 2014 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions Privacy Statement Cookie Policy Trademarks of Cisco Systems, Inc. Updated: Jul 31, 2006 Document ID: 20493