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.