Cisco Unified MeetingPlace

Document ID: 50986

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Detach the Database
Related Information

Introduction

This document provides steps to follow to detach the MPWEB Structured Query Language (SQL) database.

Note: In this document, "SQL Server" refers to any version of Microsoft SQL Server or Microsoft Desktop Engine (MSDE) mentioned in the Components Used section.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• Cisco MeetingPlace Web versions 4.2.5 and later

• MSDE versions 1.0 and 2000

• Microsoft SQL Server 7.0 and 2000

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.

Detach the Database

Complete these steps:

1. Log in as administrator on the Cisco MeetingPlace Web server. For Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, stop all MeetingPlace Web services and the WWW Publishing service. For Cisco MeetingPlace Web 4.3.0.x, stop the MeetingPlace Web Conferencing service and wait for all of the MeetingPlace Web services and the WWW Publishing service to stop.

2. If the SQL Server hosting the MPWEB database runs on the Cisco MeetingPlace Web server, proceed to the next step. If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and log in to it. If you cannot log in to that Windows server, you must log in to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so you can remotely connect to the SQL Server.

3. Go to Start > Run and issue the cmd command to access the command prompt.

4. Connect to the SQL Server by issuing the osql command with the sa account and the appropriate password, as shown here:

   C:> osql -U sa -S server_name
   
   Password: password
   1>
   

   Note: If the SQL Server runs locally, you can omit the -S server_name option. The argument server_name stands for the Windows server name

   Note: If you are not allowed to connect to this SQL Server as sa, connect using an account that has the privileges necessary to back up a database.

5. Go to the MPWEB database as shown:

   1> use mpweb
   2> go
   

6. Get a list of the database files as shown:

   1> sp_helpfile
   2> go
   name      fileid filename                 filegroup size    maxsize   growth  usage    
   --------- ------ ------------------------ --------- ------- --------- ------- ---------
   MPWEBData      1 C:\MSSQL7\Data\MPWEB.mdf PRIMARY   2432 KB Unlimited 1024 KB data only
   MPWEBLog       2 C:\MSSQL7\Data\MPWEB.ldf NULL      1280 KB Unlimited 10%     log only
   

   In this example, the MPWEB database relies on two physical files: C:\MSSQL7\Data\MPWEB.mdf and C:\MSSQL7\Data\MPWEB.ldf.

7. Move back to the SQL Server master database as shown:

   1> use master
   2> go
   

8. Detach the MPWEB database as shown:

   1> sp_detach_db 'MPWEB'
   2> go
   

9. Decide what you should do with the physical files identified during Step 6. They constitute your detached database. For example, you can archive them or use them to attach the associated MPWEB database to another SQL Server (refer to MeetingPlace Web MPWEB SQL Database Attachment).

10. If you are running Cisco MeetingPlace Web 4.3.0.x, there is a second, slave MPWEB database that needs to be detached. Its name includes a series of digits that varies from one installation to another. Issue this command to determine the slave database name on your SQL Server:

    1> select name from sysdatabases where name like 'MPWEB%'
    2> go
    ---------------------------------------------------
    name                
    [char              ]
    --------------------            
    MPWEB-Slave-37102728

    In this example, the name of the slave database is MPWEB-Slave-37102728. Execute Steps 5 through 9 again, replacing the database name "MPWEB" with "MPWEB-Slave-xxxxxxxx." The two databases are logically linked together, so if you want to archive the detached MPWEB database, you must do the same for the MPWEB-Slave-xxxxxxxx database. If you want to reattach the MPWEB database to another SQL Server, you must do the same for the MPWEB-Slave-xxxxxxxx database. Once this is done, proceed to the next step.

11. Issue the exit command to exit osql.

Related Information

• MeetingPlace Web MPWEB SQL Database Attachment
• Voice Technology Support
• Voice and IP Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support - Cisco Systems