Msde database size, Msde database scalability – Cisco Conference Phone User Manual

Page 20

Advertising
background image

2-2

Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3

OL-10029-01

Chapter 2 Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3

About the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation

All new servers being deployed must be either Cisco MCS or, for MeetingPlace customers with a legacy
system, Cisco MCS-equivalent servers.

Cisco Unified MeetingPlace Web Conferencing comes with a distributable version of SQL Server called
MSDE 2000. Although MSDE 2000 and SQL Server 2000 are based on the same technology, MSDE
2000 does not scale as well as SQL Server 2000. Because of this by-design limitation, Cisco
Unified MeetingPlace Web Conferencing customers running MSDE 2000 can encounter performance
and scalability-related problems when their usage of Cisco Unified MeetingPlace Web Conferencing
grows.

The following sections provide information about how to anticipate and diagnose performance and
scalability limitations related to MSDE:

MSDE Database Size, page 2-2

MSDE Database Scalability, page 2-2

MSDE Database Size

MSDE limits the database size to 2 GB. If either the MPWEB or the MPWEB-Slave database reaches
2 GB, the Cisco Unified MeetingPlace Web Conferencing application can fail. Therefore, you must
monitor the growth of the MPWEB databases and take one of the following actions before either
database reaches 2 GB:

Set a more aggressive value for the Purge meetings held before (Days) parameter. For more
information, see the “About the MeetingNotes Purge Parameter” section in Chapter 3 of the

Configuration Guide

for Cisco Unified MeetingPlace Web Conferencing Release 5.3.

Upgrade to a full version of SQL Server with a per processor license, as this does not have a database
size limitation.

MSDE Database Scalability

MSDE implements a concurrent workload throttle mechanism to limit scalability under heavy load.
Currently, this mechanism activates when more than eight SQL queries execute concurrently. However,
there is no direct mapping between the number of active web-conferencing users and the exceeding of
this limit.

Rather, the exceeding of this limit depends on the following:

Number of active users

Features that are used at any given time and how these features interact with the database

Current size of the database

Power of the server (CPU, disks, and so on)

Although Microsoft does not give information about the specific algorithm that is used to implement this
concurrent workload throttle mechanism, our tests show that the slowdown is based on the number of
SQL queries that exceed the limit of eight queries. For example, if 10 concurrent queries execute, the
slowdown is minimal. If 20 concurrent queries execute, the slowdown is more noticeable. If 40 or more
concurrent queries execute, the slowdown can become so significant that users find Cisco
Unified MeetingPlace Web Conferencing as unresponsive or non-functional.

Related Topics

See the “How to Assess Performance Degradation Due to the Database Scalability Limitation of
MSDE” section in the

Configuration Guide

for Cisco Unified MeetingPlace Web Conferencing

Release 5.3.

Advertising