Home > Forum > General > Two attachment databases, problem with importing test->prod.

Two attachment databases, problem with importing test->prod.

0

Maciej

18.12.2023

14:51

Maciej

We have two attachment databases, one for testing and one for production:

BPS_Content_Att_test
BPS_Content_Att_test2
BPS_Content_Att
BPS_Content_Att2

In this application we use BPS_Content_Att_test2 for testing and BPS_Content_Att2 for production. Unfortunately we don’t have a database with identical name, so when we import from test to production, the default attachment database specified in the global settings is used (BPS_Content_Att).

Is there any solution in this situation, that during the import we can use the BPS_Content_Att2 database?

Reply

18.12.2023

20:37

Hi Maciej,

when you import the process the first time, than you can select which attachment database should be used. The default database, is suggested.
If you haven't created any instance yet you can change the attachment database in the process. Maybe it's also possible to change it while there are no attachments.
I'm not to sure about it.
Afterwards you are stuck.

Best regards,
Daniel

Reply

Solution (0)

Helpful (0)

Wrong answer (0)