question

DuboseMicheleADIT-6155 avatar image
0 Votes"
DuboseMicheleADIT-6155 asked EchoDu-MSFT commented

Attach/Detach content database after applying Public Update

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?

office-sharepoint-server-administration
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @DuboseMicheleADIT-6155 ,

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!

0 Votes 0 ·
EchoDu-MSFT avatar image
0 Votes"
EchoDu-MSFT answered EchoDu-MSFT commented

Hello @DuboseMicheleADIT-6155 ,

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.




· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @EchoDu-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.

0 Votes 0 ·
EchoDu-MSFT avatar image EchoDu-MSFT DuboseMicheleADIT-6155 ·

Hi @DuboseMicheleADIT-6155

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

0 Votes 0 ·

Hi @EchoDu-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?

0 Votes 0 ·

Hi @EchoDu-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.

0 Votes 0 ·
Show more comments
trevorseward avatar image
0 Votes"
trevorseward answered

Yes, that process should work just fine.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.