dsccommunity / dsccommunity/SharePointDsc

[SPConfigWizard] Add possibility to temporarily dismount content databases during config wizard

Open
#1,413 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
C#
Stars
246
Forks
106
PR merge metrics
No merged PRs in 30d

Description

Problem description

(Idea provided by Markku Partanen)

Would it be an idea to temporarily dismount content databases before running the configuration wizard and mounting them again afterwards.

This means that without any content databases the configuration wizard will complete faster. Also, when remounting the databases again, the upgrade will run in parallel instead of sequential by running the config wizard.

Some important considerations are:

  • This has to be optional, for example by adding a parameter in which you specify all databases that have to be dismounted.
  • This only has to be done on one server. Also make sure you run this server first, for example using a WaitFor resource. Has to be done by the person creating the DSC config.
  • Questions:
    • Can the mount database run in parallel with the config wizard on another server? Will this even happen, if you have implemented using WaitFor?
    • Are content databases accessible during mount/attach/upgrade? This must be tested?
Verbose logs
N/A
DSC configuration
SPConfigWizard RunConfigWizard
{
    IsSingleInstance     = "Yes"
    DismountDatabases    = $true
    PsDscRunAsCredential = $SetupAccount
}

or 

SPConfigWizard RunConfigWizard
{
    IsSingleInstance     = "Yes"
    DismountDatabases    = @("SPContent1", "SPContent2")
    PsDscRunAsCredential = $SetupAccount
}
Suggested solution

Potentially add possibility to dismount content databases before upgrade, to speed up upgrade process.

SharePoint version and build
All
Operating system the target node is running
All
PowerShell version and build the target node is running
All
SharePointDsc version
Dev

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the SPConfigWizard DSC resource and reviewing how its RunConfigWizard configuration is handled. Determine how optional database names or a boolean would be represented, then test dismounting, wizard execution, remounting, upgrade concurrency, and the required one-server ordering before considering the work complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.