Document ID: 50040
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
DBMS Information Form
Related Information
Introduction
This document provides information to help you list and address commonly asked questions about management issues, such as SQL database networking, security, and administrations, before implementing Cisco MeetingPlace software that uses an SQL database.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on Cisco MeetingPlace Web versions: 4.2.5, 4.2.7, and 4.3.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
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
DBMS Information Form
This table addresses some commonly asked questions that come about before implementing Cisco MeetingPlace software that uses an SQL database.
|
What is the proposed use of the Database Management System (DBMS)? |
A. OLTP (On-line Transaction Processing) B. DSS (Decision Support System) C. OLAP (Online Analytical Processing) D. Data Mining E. Work Group F. Repository G. Other |
|
What is the size of the database (in MB)? |
The size varies depending on usage of product, and can grow to over 2 GB at some of the largest installations. |
|
What is the total number of tables? |
This depends on exact version of software:
|
|
What is the number of indices? |
Depends on exact version of software:
|
|
How big is the largest table (in MB)? |
The size varies depending on the number of meetings. |
|
List the DBMS availability requirements. |
It is 7x24, or inline with Cisco MeetingPlace availability. |
|
List the DBMS backup requirements. |
There are none, data is regenerated if lost (refer to Notes1 ). Required for Cisco MeetingPlace Web Conference 4.2.7 and 4.3.0 (refer to Notes2 ). |
|
List the DBMS disaster recovery requirements. |
There are none, data is regenerated if lost. |
|
List the DBMS archiving requirements. |
There are none, data is purged per product settings. |
|
Describe the update and load activity and frequency. |
Updates are made every 30 seconds, based on activity. |
|
List the required communication protocols. |
This is your choice, TCP/IP by default. |
|
Is the DB Internet accessible? |
This is not required. |
|
What is the number of concurrent users? |
Direct access to SQL db is through NT processes associated with Cisco MeetingPlace services. Services log into SQL db using the built-in ‘sa’ account (with a blank password) (refer to Notes 3 ).
|
|
Describe the nature of the DB application. |
It maintains a cache of meeting information for Cisco MeetingPlace. |
|
Is this a software package? |
Yes, the SQL Server is used and packaged as MSDE by Microsoft. |
|
If yes, list required DBMS ports and native driver availability. |
They are TCP/IP and 1433. |
|
List the required development tools. |
None. |
|
Describe the application architecture. |
NT Service accessing the database. |
|
Describe the security requirements. |
Standard database security measures. |
|
Does this DBMS interface with other data sources? |
No. |
|
Is this DBMS distributed? |
No. Note: This will be in a future version of Cisco MeetingPlace Web. |
|
Does this DBMS use specialized data types (for example, Binary Large Objects [BLOBs] and user-defined data types [UDTs])? |
No. |
|
Does this DBMS require other DBMS specific functions (for example, Stored Procedures, Triggers, DCE, and Spatial)? |
No. |
Notes
1 In most cases, the database can be rebuilt using the information on the Cisco MeetingPlace server. However, if the customer uses the NT server as an archive for Cisco MeetingPlace meetings and MeetingNotes (for example; meetings, recordings and attachments), and only keep the information for a short period of time on the Cisco MeetingPlace server before they are purged, then it is critical that customer backup the SQL database regularly.
2 Some data exists only in the SQL database and not on the Cisco MeetingPlace server. Some examples are tables associated with Rollover, Single System Image, the Web Poll features, and the Reference Center customizations.
3 By default, the Cisco MeetingPlace services use the built-in SQL account of ‘sa’ (and blank password in 4.2.7 and earlier) to access the SQL database. To use a different SQL account, or to use the ‘sa’ account but with a non-blank password, you must install the full version of Microsoft SQL Server 7 or SQL Server 2000. Refer to Tech Note Install MeetingPlace Web 4.1.3x and later when SQL sa account’s password is not blank. In Cisco MeetingPlace Web 4.3.0 and later, you may not use a blank sa password. If you have a blank password at the time you install the product, the installer will ask you for a non-blank password and it will change your blank password to the value you enter. In Cisco MeetingPlace Web 4.3.0 and later, you may use a non-sa account as well. The installer prompts for the account name and password.
4 There are some servlets and ISAPI DLLs that run inside of IIS that also access the database.
Related Information
- Voice Technology Support
- Voice and IP Communications Product Support
- Recommended Reading: Troubleshooting Cisco IP Telephony
- Technical Support - Cisco Systems
| Updated: Jan 31, 2006 | Document ID: 50040 |