dsccommunity / dsccommunity/SqlServerDsc

SqlSetup: ADVANCEDANALYTICS feature needs its own licence acceptance switch

Open
#340 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug good first issue help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Details of the scenario you try and problem that is occurring:
xSQLServer installation with ADVANCEDANALYTICS in the features string

The DSC configuration that is using the resource (as detailed as possible):

foreach($SQLServer in $Node.SQLServers)
{
        $SQLInstanceName = $SQLServer.InstanceName

        $Features = "SQLENGINE,ADVANCEDANALYTICS,FULLTEXT,DQ,RS,SQL_SHARED_MR,DQC,CONN,IS,BOL,SNAC_SDK,MDS"

        if($Features -ne "")
        {
            xSqlServerSetup ($Node.NodeName + $SQLInstanceName)
                {
                    # DependsOn = "[WindowsFeature]NET-Framework-Core"
                    SourcePath = $Node.SourcePath
                    SourceFolder = $Node.SourceFolder
                    SetupCredential = $Node.InstallerServiceAccount
                    InstanceName = $SQLInstanceName
                    Features = $Features
                    SQLSysAdminAccounts = $Node.InsallerServiceAccount
                    InstallSharedDir = "C:\Program Files\Microsoft SQL Server"
                    InstallSharedWOWDir = "C:\Program Files (x86)\Microsoft SQL Server"
                    InstanceDir = "C:\Program Files\Microsoft SQL Server"
                    InstallSQLDataDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    SQLUserDBDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    SQLUserDBLogDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    SQLTempDBDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    SQLTempDBLogDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    SQLBackupDir = "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data"
                    ASDataDir = "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data"
                    ASLogDir = "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log"
                    ASBackupDir = "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup"
                    ASTempDir = "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp"
                    ASConfigDir = "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config"
                }

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
OS: Windows Server 2012 R2
SQL Server: 2016 Developer Edition
DSC Target Node: 5.0.10586.117

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

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 at the xSqlServerSetup entry point and trace how the Features string and licence acceptance settings are handled. Compare the existing feature acceptance switches, then verify that ADVANCEDANALYTICS can be selected with its own acceptance switch and that the setup configuration remains valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, sql
Domain
databases, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.