Attach/Detach content database after applying Public Update

Question

Attach/Detach content database after applying Public Update

MDuBose 716

Hello,

I'm planning to patch my SharePoint "Test" farm. Before doing so, I want to detach the "Test" content DBs from the "Test" web application and attach the "Prod" content DBs to the "Test" web application. The purpose of this is so I can have an idea of high long the patching process will take on a Production Farm. I have taken a backup of the Prod content DBs and copied them to the "Test" DB server. The "Test" content DBs still exists. My original thought was to attach the Prod DBs to the web application, perform the patch then detach the Prod content DBs and attach the "Test" content DBs backed to the "Test" web application. Will doing so, cause issues with the SharePoint farm?

Echo Du_MSFT 17,346 Reputation points

2021-03-16T06:24:27.747+00:00

Hi @MDuBose ,

Would you tell me whether your issue has been resolved or have any update?
I am looking forward to your reply.

Have a nice day!

Answer accepted by question author

Echo Du_MSFT 17,346

Hello @MDuBose ,

Don't worry, the process can working and will not cause issues with the SharePoint farm.

For attaching or detaching content DBs in SharePoint Server, you can refer to this article.

Thanks,
Echo Du

===================

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

MDuBose 716 Reputation points

2021-03-09T14:41:19.22+00:00

Hi @Echo Du_MSFT ,

Since the purpose of attaching/detaching the Prod content DBs to the test environment is to get a feel of how long the patching process will take, is it best practice to instead, replace the Test content DBs with the Prod content DBs in the SharePoint Server? So, I would remove the Test content DBs from the DB server and rename the Prod content DBs to "Test". This is so I can always test against a production environment when running the patch.
Echo Du_MSFT 17,346 Reputation points

2021-03-10T08:05:13.197+00:00

Hi @MDuBose ，

You just attach the "Prod" content database into the "Test" DB server. This does not mean that the current environment has become a production environment.

Therefore, if you perform patching process in the "Test" environment, it is not the same as running patching process in the production environment.

Thanks,
Echo Du
MDuBose 716 Reputation points

2021-03-10T08:15:01.147+00:00

Hi @Echo Du_MSFT ,
To make sure I was clear with my question and that I understand your response, should I not replace the "Test" content DBs with "Prod" content DBs in the "Test" environment?
MDuBose 716 Reputation points

2021-03-10T14:19:56.517+00:00

Hi @Echo Du_MSFT ,
So does this means there isn't a point of attaching "Prod" content DB to my "Test" environment for my purpose? The purpose of this was so I could make "Test" environment similar to "Prod" environment to test the patching process.
Echo Du_MSFT 17,346 Reputation points

2021-03-16T03:31:14.783+00:00

Hi @MDuBose ，

Yes, there is no need to attach the "Prod" content DB to "Test" environment. Because attaching the "Prod" content DB to "Test" environment only means that the content DB from the "Prod" environment can be used in "Test" environment, not that "Test" environment has become "Prod" environment

Please test the patching process directly in the "Prod" environment.

Thanks,
Echo Du

1 additional answer

Your answer

Echo Du_MSFT 17,346 Reputation points

2021-03-16T06:24:27.747+00:00

Hi @MDuBose ,

Would you tell me whether your issue has been resolved or have any update?
I am looking forward to your reply.

Have a nice day!
MDuBose 716 Reputation points

2021-03-09T14:41:19.22+00:00

Hi @Echo Du_MSFT ,

Since the purpose of attaching/detaching the Prod content DBs to the test environment is to get a feel of how long the patching process will take, is it best practice to instead, replace the Test content DBs with the Prod content DBs in the SharePoint Server? So, I would remove the Test content DBs from the DB server and rename the Prod content DBs to "Test". This is so I can always test against a production environment when running the patch.
Echo Du_MSFT 17,346 Reputation points

2021-03-10T08:05:13.197+00:00

Hi @MDuBose ，

You just attach the "Prod" content database into the "Test" DB server. This does not mean that the current environment has become a production environment.

Therefore, if you perform patching process in the "Test" environment, it is not the same as running patching process in the production environment.

Thanks,
Echo Du
MDuBose 716 Reputation points

2021-03-10T08:15:01.147+00:00

Hi @Echo Du_MSFT ,
To make sure I was clear with my question and that I understand your response, should I not replace the "Test" content DBs with "Prod" content DBs in the "Test" environment?
MDuBose 716 Reputation points

2021-03-10T14:19:56.517+00:00

Hi @Echo Du_MSFT ,
So does this means there isn't a point of attaching "Prod" content DB to my "Test" environment for my purpose? The purpose of this was so I could make "Test" environment similar to "Prod" environment to test the patching process.
Echo Du_MSFT 17,346 Reputation points

2021-03-16T03:31:14.783+00:00

Hi @MDuBose ，

Yes, there is no need to attach the "Prod" content DB to "Test" environment. Because attaching the "Prod" content DB to "Test" environment only means that the content DB from the "Prod" environment can be used in "Test" environment, not that "Test" environment has become "Prod" environment

Please test the patching process directly in the "Prod" environment.

Thanks,
Echo Du

Answer 1

trevorseward 11,711

Yes, that process should work just fine.

0 comments

Share via

Attach/Detach content database after applying Public Update

1 additional answer

Your answer