backup and reload Enterprise Resources?

[SusanC]

My client wants to create a new database instance for the new year. Some
project plans will be reloaded onto the system but the majority will be
archived. Because of this, it is essential that the Enterprise Global and
Enterprise Resources be copied to the new instance.

The instance was created and the Enterprise Global backed up from the old
instance and reloaded onto the new one.

Does anyone have a simple way to backup and reload the Enterprise Resource
pool? This must allow the active and inactive resources to be loaded.

Thank you,
SusanC

 

[Ray McCoppin]

Open a new project on the original instance, add all of the enterprise
reosurces to this project using build team. Save this project as a MPP file.

On the new instance import the resources from this mpp file. Assign these
resources to a project and publish the assignments. They will all be team
member now. Use the PWA admin to add resources to the Project Managers, and
excutives role.

Hope this helps.

 

[SusanC]

Dear Ray,

I tried the procedure and only the active resources were loaded. Also, the
Enterprise Unique IDs are different than on the old database instance. This
means the project plans cannot be imported from the old to the new database
instance.

Does anyone know how to load the active and inactive resources and keep the
Enterprise Unique IDs the same?

Thanks!

 

[Ray McCoppin]

If the previous will not work. I would backup the old database and restore
it to the new instance. Then us the PSCleaner tool to remove the projects
you don't want to keep.

 

[Gary L. Chefetz [MVP]]

Susan:

Just to be clear, you are incorrect that preserving the EUIDs for resources
is necessary using the procedure Ray outlined. If you use the Import Project
to Enterprise, you'll have the opportunity to map the resources. The EUIDs
will be reassigned accordingly.

If you want to include inactive resources using this procedure, then you
must make them active, temporarily. I'd also recommend adding your custom
fields to the resource sheet view and copy the values into corresponding
local fields to preserve these correctly. Once again, you'll be able to map
these during the import process.

The only way to preserve everything is to use the database restore method
Ray gave you as an alternative.

 

[wbbusby]

I'm struggling with the same issues outlined here and had chosen to migrate
databases, then clean out old projects. Made sense and basically all my
resources and enterprise outline codes came across just as I'd wanted. My
issues are around the data that is already populated in pending time updates,
PWA, etc. Should wiping all projects also clean out all this extraneous data?

Susan:

Just to be clear, you are incorrect that preserving the EUIDs for resources
is necessary using the procedure Ray outlined. If you use the Import Project
to Enterprise, you'll have the opportunity to map the resources. The EUIDs
will be reassigned accordingly.

If you want to include inactive resources using this procedure, then you
must make them active, temporarily. I'd also recommend adding your custom
fields to the resource sheet view and copy the values into corresponding
local fields to preserve these correctly. Once again, you'll be able to map
these during the import process.

The only way to preserve everything is to use the database restore method
Ray gave you as an alternative.

 

[Gary L. Chefetz [MVP]]

When you delete projects, the updates associated with them are deleted as
well. If you have updates pending that are orphaned records, you'll need to
do some work directly in the table to clean these up. Does that help?