Landscape

[Former Member]

Dear Experts,

Which of the following methode is recommanded by SAP to pass from DEV --> Quality --> Prod

1 - Create master/slave

2 - Export/Import scemas

3 - Archive/Unarchive repositories

And WHY?

Regards,

NL

[michael_theis · Accepted solution]

Hi guys,

1 - Create master/slave

You cannot use master/slave for this purpose. A slave is always a read-only copy of the master, meaning you cannot change any data in this kind of repository. Like Amol said, you can use it as a backup strategy or to allow read only access to your data.

2 - Export/Import schemas

Export/import schemas is the way to go if you do updates in your DEV repository and if you already have existing Q and PROD repositories. Note: Import and Syndication maps are not yet included in this transport! They have to be exported/imported (or even created) manually.

3 - Archive/Unarchive repositories

This is the option if you create new Q and PROD repositories from you DEV repository. Just check the archive options when you create the archive. There you can exclude the data, meaning that your archive contains the strubture and import/syndication maps only.

BR Michael

[Former Member]

Hi User NL,

upto SP04 its option: c using archive and unarchive.

but from SP05, i think u can use master slave so its option: a

rewards if helpful.

Regards,

Alok

[Former Member]

Hi ,

It should be "Export / Import Schemas".

Create master/slave

Its altogether a different scenario. Its basically used as an option for "Backup Strategy".

Export/Import scemas

Used to transport Repository Field/Tables/administrative data but not actually the (Main table / Sub tables) data.

This method is recommended if you have any field/table level transports. Advantage of this method is it prompts and asks user before we commit any changes to repository.

We have an option to keep existing repository as it is or accept whatever coming in from transport.

Archive/Unarchive repositories

Used to transport Repository Field/Tables/administrative data as well as main table/sub table/workflows data. It actually copies each and every single information of source repository.

It doesnt come up with what are all the changes it will be doing into target repository and just overwrites the existing data.

Also its very important to take care of User mapping information (User ID + Password) if you are considering archive/unarchive for transports.

Regards,

Amol