Updated the script with additional steps for killing the ongoing proc…

[ronazi]

…esses and also sp_reconfigure options

Running just those (on the current doc) will error out with multiple errors and customers will need to go back and forth in troubleshooting the errors. Hence edited the doc with detailed step by step guide.

[ghost]

All CLA requirements met.

[PRMerger15]

@ronazi : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[VanMSFT]

Hi @ronazi - Thanks for the proposed changes.

@bluefooted - Hey Pam, do you mind taking a quick look at the proposed changes? Do you agree with providing instructions to kill all SPIDs above 50 before changing the containment option? At the very least, we will need to put a warning in place. Thanks!

[ronazi]

@VanMSFT What is the status on this?

[bluefooted]

Sorry folks, just got back from vacation! No, the kill script isn't the best way to do this, we would normally recommend something like the following script:

ALTER DATABASE Test
SET SINGLE_USER -- or RESTRICTED_USER for Managed Instance
WITH ROLLBACK IMMEDIATE;

ALTER DATABASE Test
SET containment=partial;

ALTER DATABASE Test
SET MULTI_USER;

And yes I agree, if we add this, we should also add a warning.

[PRMerger7]

@VanMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[VanMSFT]

Thanks Pam!

@ronazi - I made edits to your PR based on Pam's suggestion. Thanks for the help with our documentation. Let me know if there are any issues. I will approve this PR now.

#sign-off

[bluefooted]

Looks good, thank you!

[PRMerger16]

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.