v15.2.0

[v15.2.0]

Changed

• SqlServerDsc
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.
  • Updated pipeline configuration to align with the latest changes in Sampler.
  • Update codecov.yml to support carry forward flags.
  • Updated pipelines files to latest from Sampler project.
  • Updated GitHub issue templates.
  • Remove pipeline jobs Test_Integration_SQL2016, Test_Integration_SQL2017,
    and Test_Integration_SQL2019 and raplaced with a single job
    Test_Integration (issue #1713).
  • Update HQRM tests to run on the VM image windows-2022.
  • Update unit tests to run on the VM image windows-2022.
  • Update integration tests to run both on Windows Server 2019 and Windows
    Server 2022 (issue #1713).
• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
• SqlAgentAlert
  • Switched README file with SqlAgentFailsafe (issue #1709).
• SqlAgentFailsafe
  • Switched README file with SqlAgentAlert (issue #1709).

Added

• SqlMemory
  • Added two new optional parameters MinMemoryPercent and MaxMemoryPercent.
    Provides the ability to set the minimum and/or maximum buffer pool used by
    the SQL Server instance as a percentage of total server memory.
    (issue #1397).
• SqlRSSetup
  • Integration tests now install Microsoft SQL Server 2019 Reporting Services
    (issue #1717).
• SqlRS
  • Integration tests now configures Microsoft SQL Server 2019 Reporting Services.

Fixed

• SqlSetup
  • Fixed integration tests for SQL Server 2016 and SQL Server 2017.
• SqlServerDsc.Common
  • Fixed so that CredScan no longer reports a password false-positive
    (issue #1712).
• SqlRS
  • Fixed SSRS 2019 initialization (issue #1509).
  • Fix a problem that did not correctly evaluate the UseSSL property against
    the current state.

v15.2.0-preview0005

[v15.2.0-preview0005]

Changed

• SqlServerDsc
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.
  • Updated pipeline configuration to align with the latest changes in Sampler.
  • Update codecov.yml to support carry forward flags.
  • Updated pipelines files to latest from Sampler project.
  • Updated GitHub issue templates.
  • Remove pipeline jobs Test_Integration_SQL2016, Test_Integration_SQL2017,
    and Test_Integration_SQL2019 and raplaced with a single job
    Test_Integration (issue #1713).
  • Update HQRM tests to run on the VM image windows-2022.
  • Update unit tests to run on the VM image windows-2022.
  • Update integration tests to run both on Windows Server 2019 and Windows
    Server 2022 (issue #1713).
• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
• SqlAgentAlert
  • Switched README file with SqlAgentFailsafe (issue #1709).
• SqlAgentFailsafe
  • Switched README file with SqlAgentAlert (issue #1709).

Added

• SqlMemory
  • Added two new optional parameters MinMemoryPercent and MaxMemoryPercent.
    Provides the ability to set the minimum and/or maximum buffer pool used by
    the SQL Server instance as a percentage of total server memory.
    (issue #1397).
• SqlRSSetup
  • Integration tests now install Microsoft SQL Server 2019 Reporting Services
    (issue #1717).
• SqlRS
  • Integration tests now configures Microsoft SQL Server 2019 Reporting Services.

Fixed

• SqlSetup
  • Fixed integration tests for SQL Server 2016 and SQL Server 2017.
• SqlServerDsc.Common
  • Fixed so that CredScan no longer reports a password false-positive
    (issue #1712).
• SqlRS
  • Fixed SSRS 2019 initialization (issue #1509).
  • Fix a problem that did not correctly evaluate the UseSSL property against
    the current state.

v15.2.0-preview0004

[v15.2.0-preview0004]

Changed

• SqlServerDsc
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.
  • Updated pipeline configuration to align with the latest changes in Sampler.
  • Update codecov.yml to support carry forward flags.
• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
• SqlAgentAlert
  • Switched README file with SqlAgentFailsafe. Issue #1709.
• SqlAgentFailsafe
  • Switched README file with SqlAgentAlert. Issue #1709.

Added

• SqlMemory
  • Added two new optional parameters MinMemoryPercent and MaxMemoryPercent.
    Provides the ability to set the minimum and/or maximum buffer pool used by
    the SQL Server instance as a percentage of total server memory.
    (issue #1397).

Fixed

• SqlSetup
  • Fixed integration tests for SQL Server 2016 and SQL Server 2017.

v15.2.0-preview0003

[v15.2.0-preview0003]

Changed

• SqlServerDsc
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.
  • Updated pipeline configuration to align with the latest changes in Sampler.
• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.

Added

• SqlMemory
  • Added two new optional parameters MinMemoryPercent and MaxMemoryPercent.
    Provides the ability to set the minimum and/or maximum buffer pool used by
    the SQL Server instance as a percentage of total server memory.
    (issue #1397).

Fixed

• SqlSetup
  • Fixed integration tests for SQL Server 2016 and SQL Server 2017.

v15.2.0-preview0002

[v15.2.0-preview0002]

Changed

• SqlServerDsc
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.
• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.

Added

• SqlMemory
  • Added two new optional parameters MinMemoryPercent and MaxMemoryPercent.
    Provides the ability to set the minimum and/or maximum buffer pool used by
    the SQL Server instance as a percentage of total server memory.
    (issue #1397).

v15.2.0-preview0001

[v15.2.0-preview0001]

Changed

• SqlSetup
  • The helper function Connect-SqlAnalysis was using LoadWithPartial()
    to load the assembly Microsoft.AnalysisServices. On a node where multiple
    instances with different versions of SQL Server (regardless of features)
    is installed, this will result in the first assembly found in the
    GAC will be loaded into the session, not taking versions into account.
    This can result in an assembly version being loaded that is not compatible
    with the version of SQL Server it was meant to be used with.
    A new method of loading the assembly Microsoft.AnalysisServices was
    introduced under a feature flag; 'AnalysisServicesConnection'.
    This new functionality depends on the SqlServer
    module, and must be present on the node. The SqlServer
    module can be installed on the node by leveraging the new DSC resource
    PSModule in the PowerShellGet
    module (v2.1.2 and higher). This new method does not work with the
    SQLPS module due to the SQLPS module does not load the correct assembly,
    while SqlServer
    module (v21.1.18080 and above) does. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Under a feature flag 'AnalysisServicesConnection'. The detection of
    a successful connection to the SQL Server Analysis Services has also been
    changed. Now it actually evaluates the property Connected of the returned
    Microsoft.AnalysisServices.Server object. The new functionality is used
    when the parameter FeatureFlag is set to 'AnalysisServicesConnection'.
    This functionality will be the default in a future breaking release.
  • Changed to the new GitHub deploy tasks that is required for the latest
    version of the Sampler module.

v15.1.1

[v15.1.1]

Fixed

• SqlTraceFlag
  • Fixed $null reference error when no actual trace flags are present.
    Added two arrays to prevent a $null reference at compare-object
    (issue #1688).
• SqlServerDsc
  • Removed a left-over comment in the file analyzersettings.psd1.

v15.1.1-preview0001

[v15.1.1-preview0001]

Fixed

• SqlTraceFlag
  • Fixed $null reference error when no actual trace flags are present.
    Added two arrays to prevent a $null reference at compare-object
    (issue #1688).
• SqlServerDsc
  • Removed a left-over comment in the file analyzersettings.psd1.

v15.1.0

[v15.1.0]

Added

• SqlServerDsc
  • Added a new script analyzer rule to verify that Import-SQLPSModule or Connect-SQL
    (that implicitly calls Import-SQLPSModule) is present in each Get-, Test-,
    and Set-TargetResource function. If neither command is not needed then the
    analyzer rule should be overridden (issue #1683).
  • Added a new pipeline job that runs Script Analyzer on all PowerShell scripts
    in the source folder. The rules are defined by the Script Analyzer settings
    file .vscode\analyzersettings.psd1 (which also the Visual Studio Code
    PowerShell extension uses).
  • Added unit tests and integration tests for SQL Server 2019
    (issue #1310).

Changed

• SqlServerDsc
  • Suppressed new custom Script Analyzer rule SqlServerDsc.AnalyzerRules\Measure-CommandsNeededToLoadSMO
    for Get-, Test-, and Set-TargetResource functions in the resources.
• SqlLogin
  • Added functionality to throw exception if an update to the LoginMustChangePassword
    value on an existing SQL Login is attempted. This functionality is not supported
    by referenced, SQL Server Management Object (SMO), libraries and cannot be
    supported directly by this module.
  • Added integration tests to ensure that an added (or updated) SqlLogin can
    connect into a SQL instance once added (or updated).
  • Added integration tests to ensure that the default database connected to by
    a SqlLogin is the same as specified in the resource's DefaultDatabase
    property/parameter.
  • Amended how the interdependent, PasswordExpirationEnabled and PasswordPolicyEnforced
    properties/parameters are updated within the SqlLogin resource - Both values
    are now updated together if either one or both are not currently in the desired
    state. This change avoids exceptions thrown by transitions to valid, combinations
    of these properties that have to transition through an invalid combination (e.g.
    where PasswordExpirationEnabled is $true but PasswordPolicyEnforced is
    $false).
• SqlSetup
  • Minor refactor due to source code lint errors. The loop what evaluates
    the configuration parameters *FailoverCluster was change to a foreach().

Fixed

• SqlServerDsc
  • The component gitversion that is used in the pipeline was wrongly
    configured when the repository moved to the new default branch main.
    It no longer throws an error when using newer versions of GitVersion
    (issue #1674).
  • Minor lint errors throughout the repository.
• SqlLogin
  • Added integration tests to assert LoginPasswordExpirationEnabled,
    LoginPasswordPolicyEnforced and LoginMustChangePassword properties/parameters
    are applied and updated correctly. Similar integration tests also added to ensure
    the password of the SqlLogin is updated if the password within the SqlCredential
    value/object is changed (issue #361,
    issue #1032 and
    issue #1050).
  • Updated SqlLogin, integration tests to make use of amended Wait-ForIdleLcm,
    helper function, -Clear switch usage to remove intermittent, integration
    test failures (issue #1634).
• SqlRSSetup
  • If parameter SuppressRestart is set to $false the /norestart
    argument is no longer wrongly added (issue #1401).
• SqlSetup
  • Added/corrected InstallSharedDir, property output when using SQL Server 2019.
• SqlTraceFlag
  • Fixed Assembly not loaded error (issue #1680).
• SqlDatabaseUser
  • Added parameter ServerName to the call of Assert-SqlLogin.
    @PSBoundParameters doesn't capture the default value of ServerName
    when it is not explicitly set by the caller (issue #1647).

v15.1.0-preview0002

[v15.1.0-preview0002]

Added

• SqlServerDsc
  • Added a new script analyzer rule to verify that Import-SQLPSModule or Connect-SQL
    (that implicitly calls Import-SQLPSModule) is present in each Get-, Test-,
    and Set-TargetResource function. If neither command is not needed then the
    analyzer rule should be overridden (issue #1683).
  • Added a new pipeline job that runs Script Analyzer on all PowerShell scripts
    in the source folder. The rules are defined by the Script Analyzer settings
    file .vscode\analyzersettings.psd1 (which also the Visual Studio Code
    PowerShell extension uses).
  • Added unit tests and integration tests for SQL Server 2019
    (issue #1310).

Changed

• SqlServerDsc
  • Suppressed new custom Script Analyzer rule SqlServerDsc.AnalyzerRules\Measure-CommandsNeededToLoadSMO
    for Get-, Test-, and Set-TargetResource functions in the resources.
• SqlLogin
  • Added functionality to throw exception if an update to the LoginMustChangePassword
    value on an existing SQL Login is attempted. This functionality is not supported
    by referenced, SQL Server Management Object (SMO), libraries and cannot be
    supported directly by this module.
  • Added integration tests to ensure that an added (or updated) SqlLogin can
    connect into a SQL instance once added (or updated).
  • Added integration tests to ensure that the default database connected to by
    a SqlLogin is the same as specified in the resource's DefaultDatabase
    property/parameter.
  • Amended how the interdependent, PasswordExpirationEnabled and PasswordPolicyEnforced
    properties/parameters are updated within the SqlLogin resource - Both values
    are now updated together if either one or both are not currently in the desired
    state. This change avoids exceptions thrown by transitions to valid, combinations
    of these properties that have to transition through an invalid combination (e.g.
    where PasswordExpirationEnabled is $true but PasswordPolicyEnforced is
    $false).
• SqlSetup
  • Minor refactor due to source code lint errors. The loop what evaluates
    the configuration parameters *FailoverCluster was change to a foreach().

Fixed

• SqlServerDsc
  • The component gitversion that is used in the pipeline was wrongly
    configured when the repository moved to the new default branch main.
    It no longer throws an error when using newer versions of GitVersion
    (issue #1674).
  • Minor lint errors throughout the repository.
• SqlLogin
  • Added integration tests to assert LoginPasswordExpirationEnabled,
    LoginPasswordPolicyEnforced and LoginMustChangePassword properties/parameters
    are applied and updated correctly. Similar integration tests also added to ensure
    the password of the SqlLogin is updated if the password within the SqlCredential
    value/object is changed (issue #361,
    issue #1032 and
    issue #1050).
  • Updated SqlLogin, integration tests to make use of amended Wait-ForIdleLcm,
    helper function, -Clear switch usage to remove intermittent, integration
    test failures (issue #1634).
• SqlRSSetup
  • If parameter SuppressRestart is set to $false the /norestart
    argument is no longer wrongly added (issue #1401).
• SqlSetup
  • Added/corrected InstallSharedDir, property output when using SQL Server 2019.
• SqlTraceFlag
  • Fixed Assembly not loaded error (issue #1680).
• SqlDatabaseUser
  • Added parameter ServerName to the call of Assert-SqlLogin.
    @PSBoundParameters doesn't capture the default value of ServerName
    when it is not explicitly set by the caller (issue #1647).