dsccommunity / dsccommunity/SqlServerDsc

SqlDatabase: Should Be Cluster Aware

Open
#873 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerDatabase resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.

The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a FCI.

xSQLServerDatabase Create_Database
{
    Ensure          = 'Present'
    SQLServer       = 'SQLServer'
    SQLInstanceName = 'DSC'
    Name            = 'Contoso'
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

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 tracing the xSQLServerDatabase resource behavior when the configuration is applied to multiple nodes in a Failover Cluster Instance (FCI). Reproduce the scenario with the provided Create_Database configuration; done means only the node currently hosting the instance connects and ensures the desired database state.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
databases, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.