Duplicate a Project

Duplicating a project is an important part of the application life cycle. If you want to copy objects between two projects, MicroStrategy recommends that the projects have related schemas. This means that one must have originally been a duplicate of the other, or both must have been duplicates of a third project.

Autostyles, which give a uniform appearance to reports, can be freely moved between projects regardless of whether their schemas are related. For instructions on migrating autostyles between projects, see the Advanced Reporting Help.

Project duplication is done using the Project Duplication Wizard. For detailed information about the duplication process, including step-by-step instructions, see The Project Duplication Wizard.

You can duplicate a MicroStrategy project in one of the following ways:

• From a three-tier (server) project source to a three-tier (server) project source
• From a three-tier (server) project source to a two-tier (direct) project source
• From a two-tier (direct) project source to a two-tier (direct) project source
• From a two-tier (direct) project source to a three-tier (server) project source

A server (three-tier) project source is connected to an Intelligence Server, and has the full range of administrative options available. A direct (two-tier) project source is not connected to an Intelligence Server. For more information on three-tier and two-tier project sources, see the Project Design Help.

Do not refresh the warehouse catalog in the destination project. Refresh the warehouse catalog in the source project, and then use Object Manager to move the updated objects into the destination project. For information about the warehouse catalog, see the Optimizing and Maintaining your Project section in the Project Design Help.