Skip to content

Releases: dsccommunity/SqlServerDsc

v11.1.0

25 Dec 09:15
4a68bac
Compare
Choose a tag to compare
  • Changes to SqlServerDsc
    • Updated the PULL_REQUEST_TEMPLATE with an improved task list and modified
      some text to be clearer (issue #973).
    • Updated the ISSUE_TEMPLATE to hopefully be more intuitive and easier to use.
    • Added information to ISSUE_TEMPLATE that issues must be reproducible in
      SqlServerDsc resource module (if running the older xSQLServer resource module)
      (issue #1036).
    • Updated ISSUE_TEMPLATE.md with a note about sensitive information (issue #1092).
  • Changes to SqlServerLogin
  • Changes to SqlSetup
    • Michael Fyffe (@TraGicCode): Clarify usage
      of 'SecurityMode' along with adding parameter validations for the only 2
      supported values (issue #1010).
    • Now accounts containing '$' will be able to be used for installing
      SQL Server. Although, if the account ends with '$' it is considered a
      Managed Service Account (issue #1055).
  • Changes to Integration Tests
  • Changes to Unit Tests

v11.0.0

25 Dec 09:14
026102d
Compare
Choose a tag to compare
  • Changes to SqlServerDsc
    • BREAKING CHANGE: Resource SqlRSSecureConnectionLevel was remove
      (issue #990).
      The parameter that was set using that resource has been merged into resource
      SqlRS as the parameter UseSsl. The UseSsl parameter is of type boolean. This
      change was made because from SQL Server 2008 R2 this value is made an on/off
      switch. Read more in the article ConfigurationSetting Method - SetSecureConnectionLevel.
    • Updated so that named parameters are used for New-Object cmdlet. This was
      done to follow the style guideline.
    • Updated manifest and license to reflect the new year
      (issue #965).
    • Added a README.md under Tests\Integration to help contributors to write
      integration tests.
    • Added 'Integration tests' section in the CONTRIBUTING.md.
    • The complete examples were removed. They were no longer accurate and some
      referenced resources that no longer exist. Accurate examples can be found
      in each specific resource example folder. Examples for installing Failover Cluster
      can be found in the resource examples folders in the xFailOverCluster
      resource module (issue #462).
    • A README.md was created under the Examples folder to be used as reference how
      to install certain scenarios (issue #462).
    • Removed the local specific common test for compiling examples in this repository
      and instead opted-in for the common test in the 'DscResource.Tests' repository
      (issue #669).
    • Added new resource SqlServerDatabaseMail for configuring SQL Server
      Database Mail (issue #155).
    • Updated the helper function Test-SQLDscParameterState to handle the
      data type UInt16.
    • Fixed typo in SqlServerDscCommon.Tests.
    • Updated README.md with known issue section for each resource.
    • Resources that did not have a description in the README.md now has one.
    • Resources that missed links to the examples in the README.md now has those
      links.
    • Style changes in all examples, removing type [System.Management.Automation.Credential()]
      from credential parameters (issue #1003),
      and renamed the credential parameter so it is not using abbreviation.
    • Updated the security token for AppVeyor status badge in README.md. When we
      renamed the repository the security token was changed
      (issue #1012).
    • Now the helper function Restart-SqlService, after restarting the SQL Server
      service, does not return until it can connect to the SQL Server instance, and
      the instance returns status 'Online' (issue #1008).
      If it fails to connect within the timeout period (defaults to 120 seconds) it
      throws an error.
    • Fixed typo in comment-base help for helper function Test-AvailabilityReplicaSeedingModeAutomatic.
    • Style cleanup in helper functions and tests.
  • Changes to SqlAG
    • Fixed typos in tests.
    • Style cleanup in code and tests.
  • Changes to SqlAGDatabase
    • Style cleanup in code and tests.
  • Changes to SqlAGListener
    • Fixed typo in comment-based help.
    • Style cleanup in code and tests.
  • Changes to SqlAGReplica
    • Minor code style cleanup. Removed unused variable and instead piped the cmdlet
      Join-SqlAvailabilityGroup to Out-Null.
    • Fixed minor typos in comment-based help.
    • Fixed minor typos in comment.
    • Style cleanup in code and tests.
    • Updated description for parameter Name in README.md and in comment-based help
      (issue #1034).
  • Changes to SqlAlias
    • Fixed issue where exception was thrown if reg keys did not exist
      (issue #949).
    • Style cleanup in tests.
  • Changes to SqlAlwaysOnService
    • Refactor integration tests slightly to improve run time performance
      (issue #1001).
    • Style cleanup in code and tests.
  • Changes to SqlDatabase
    • Fix minor Script Analyzer warning.
  • Changes to SqlDatabaseDefaultLocation
    • Refactor integration tests slightly to improve run time performance
      (issue #1001).
    • Minor style cleanup of code in tests.
  • Changes to SqlDatabaseRole
    • Style cleanup in tests.
  • Changes to SqlRS
    • Replaced Get-WmiObject with Get-CimInstance to fix Script Analyzer warnings
      (issue #264).
    • Refactored the resource to use Invoke-CimMethod.
    • Added parameter UseSsl which when set to $true forces connections to the
      Reporting Services to use SSL when connecting (issue #990).
    • Added complete example for SqlRS (based on the integration tests)
      (issue #634).
    • Refactor integration tests slightly to improve run time performance
      (issue #1001).
    • Style cleanup in code and tests.
  • Changes to SqlScript
    • Style cleanup in tests.
    • Updated examples.
    • Added integration tests.
    • Fixed minor typos in comment-based help.
    • Added new example based on integration test.
  • Changes to SqlServerConfiguration
    • Fixed minor typos in comment-based help.
    • Now the verbose message say what option is changing and to what value
      (issue #1014).
    • Changed the RestartTimeout parameter from type SInt32 to type UInt32.
    • Added localization (issue #605).
    • Style cleanup in code and tests.
  • Changes to SqlServerEndpoint
    • Updated README.md with links to the examples
      (issue #504).
    • Style cleanup in tests.
  • Changes to SqlServerLogin
    • Added integration tests (issue #748).
    • Minor code style cleanup.
    • Removed unused variable and instead piped the helper function Connect-SQL to
      Out-Null.
    • Style cleanup in tests.
  • Changes to SqlServerMaxDop
    • Minor style changes in the helper function Get-SqlDscDynamicMaxDop.
  • Changes to SqlServerMemory
    • Style cleanup in code and tests.
  • Changes to SqlServerPermission
    • Fixed minor typos in comment-based help.
    • Style cleanup in code.
  • Changes to SqlServerReplication
    • Fixed minor typos in verbose messages.
    • Style cleanup in tests.
  • Changes to SqlServerNetwork
    • Added sysadmin account parameter usage to the examples.
  • Changes to SqlServerReplication
  • Changes to SqlServerRole
    • Added localization (issue #621).
    • Added integration tests (issue #756).
    • Updated example to add two server roles in the same configuration.
    • Style cleanup in tests.
  • Changes to SqlServiceAccount
    • Default services are now properly detected
      (issue #930).
    • Made the description of parameter RestartService more descriptive
      (issue #960).
    • Added a read-only parameter ServiceAccountName so that the service account
      name is correctly returned as a string (issue #982).
    • Added integration tests (issue #980).
    • The timing issue that the resource returned before SQL Server service was
      actually restarted has been solved by a change in the helper function
      Restart-SqlService (issue #1008).
      Now Restart-SqlService waits for the instance to return status 'Online' or
      throws an error saying it failed to connect within the timeout period.
    • Style cleanup in code and tests.
  • Changes to SqlSetup
    • Added parameter ASServerMode to support installing Analysis Services in
      Multidimensional mode, Tabular mode and PowerPivot mode
      (issue #388).
    • Added integration tests for testing Analysis Services Multidimensional mode
      and Tabular mode.
    • Cleaned up integration tests.
    • Added integration tests for installing a default instance of Database Engine.
    • Refactor integration tests slightly to improve run time performance
      (issue #1001).
    • Added PSSA rule 'PSUseDeclaredVarsMoreThanAssignments' override in the
      function Set-TargetResource for the variable $global:DSCMachineStatus.
    • Style cleanup in code and tests.
  • Changes to SqlWaitForAG
    • Style cleanup in code.
  • Changes to SqlWindowsFirewall
    • Fixed minor typos in comment-based help.
    • Style cleanup in code.

v10.0.0

25 Dec 09:14
ef62dfa
Compare
Choose a tag to compare
  • BREAKING CHANGE: Resource module has been renamed to SqlServerDsc
    (issue #916).
  • BREAKING CHANGE: Significant rename to reduce length of resource names
    • See issue #851 for a
      complete table mapping rename changes.
    • Impact to all resources.
  • Changes to CONTRIBUTING.md
    • Added details to the naming convention used in SqlServerDsc.
  • Changes to SqlServerDsc
    • The examples in the root of the Examples folder are obsolete. A note was
      added to the comment-based help in each example stating it is obsolete.
      This is a temporary measure until they are replaced
      (issue #904).
    • Added new common test (regression test) for validating the long path
      issue for compiling resources in Azure Automation.
    • Fix resources in alphabetical order in README.md (issue #908).
  • Changes to SqlAG
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
    • BREAKING CHANGE: The read-only property SQLServerNetName was removed in favor
      of EndpointHostName (issue #924).
      Get-TargetResource will now return the value of property NetName
      for the property EndpointHostName.
  • Changes to SqlAGDatabase
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
    • Changed the Get-MatchingDatabaseNames function to be case insensitive when
      matching database names (issue #912).
  • Changes to SqlAGListener
    • BREAKING CHANGE: Parameter NodeName has been renamed to ServerName
      (issue #308).
  • Changes to SqlAGReplica
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
    • BREAKING CHANGE: Parameters PrimaryReplicaSQLServer and PrimaryReplicaSQLInstanceName
      has been renamed to PrimaryReplicaServerName and PrimaryReplicaInstanceName
      respectively (issue #922).
    • BREAKING CHANGE: The read-only property SQLServerNetName was removed in favor
      of EndpointHostName (issue #924).
      Get-TargetResource will now return the value of property NetName
      for the property EndpointHostName.
  • Changes to SqlAlwaysOnService
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlDatabase
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes SqlDatabaseDefaultLocation
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlDatabaseOwner
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlDatabasePermission
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlDatabaseRecoveryModel
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlDatabaseRole
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlRS
    • BREAKING CHANGE: Parameters RSSQLServer and RSSQLInstanceName has been renamed
      to DatabaseServerName and DatabaseInstanceName respectively
      (issue #923).
  • Changes to SqlServerConfiguration
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerEndpoint
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerEndpointPermission
    • BREAKING CHANGE: Parameter NodeName has been renamed to ServerName
      (issue #308).
    • Now the examples files have a shorter name so that resources will not fail
      to compile in Azure Automation (issue #934).
  • Changes to SqlServerEndpointState
    • BREAKING CHANGE: Parameter NodeName has been renamed to ServerName
      (issue #308).
  • Changes to SqlServerLogin
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerMaxDop
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerMemory
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerNetwork
    • BREAKING CHANGE: Parameters SQLServer has been renamed to ServerName
      (issue #308).
  • Changes to SqlServerPermission
    • BREAKING CHANGE: Parameter NodeName has been renamed to ServerName
      (issue #308).
  • Changes to SqlServerRole
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).
  • Changes to SqlServerServiceAccount
    • BREAKING CHANGE: Parameters SQLServer and SQLInstanceName has been renamed
      to ServerName and InstanceName respectively
      (issue #308).

v9.0.0

25 Dec 09:14
9a9e24d
Compare
Choose a tag to compare
  • Changes to xSQLServer
    • Updated Pester syntax to v4
    • Fixes broken links to issues in the CHANGELOG.md.
  • Changes to xSQLServerDatabase
    • Added parameter to specify collation for a database to be different from server
      collation (issue #767).
    • Fixed unit tests for Get-TargetResource to ensure correctly testing return
      values (issue #849)
  • Changes to xSQLServerAlwaysOnAvailabilityGroup
    • Refactored the unit tests to allow them to be more user friendly and to test
      additional SQLServer variations.
      • Each test will utilize the Import-SQLModuleStub to ensure the correct
        module is loaded (issue #784).
    • Fixed an issue when setting the SQLServer parameter to a Fully Qualified
      Domain Name (FQDN) (issue #468).
    • Fixed the logic so that if a parameter is not supplied to the resource, the
      resource will not attempt to apply the defaults on subsequent checks
      (issue #517).
    • Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
      the resource will only determine if a change is needed if the target node
      is the active host of the SQL Server instance (issue #868).
  • Changes to xSQLServerAlwaysOnAvailabilityGroupDatabaseMembership
    • Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
      the resource will only determine if a change is needed if the target node
      is the active host of the SQL Server instance (issue #869).
  • Changes to xSQLServerAlwaysOnAvailabilityGroupReplica
    • Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
      the resource will only determine if a change is needed if the target node is
      the active host of the SQL Server instance (issue #870).
  • Added the CommonTestHelper.psm1 to store common testing functions.
    • Added the Import-SQLModuleStub function to ensure the correct version of the
      module stubs are loaded (issue #784).
  • Changes to xSQLServerMemory
    • Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
      the resource will only determine if a change is needed if the target node
      is the active host of the SQL Server instance (issue #867).
  • Changes to xSQLServerNetwork
    • BREAKING CHANGE: Renamed parameter TcpDynamicPorts to TcpDynamicPort and
      changed type to Boolean (issue #534).
    • Resolved issue when switching from dynamic to static port.
      configuration (issue #534).
    • Added localization (en-US) for all strings in resource and unit tests
      (issue #618).
    • Updated examples to reflect new parameters.
  • Changes to xSQLServerRSConfig
    • Added examples
  • Added resource
  • Changes to xSQLServerEndpointPermission
    • Fixed a problem when running the tests locally in a PowerShell console it
      would ask for parameters (issue #897).
  • Changes to xSQLServerAvailabilityGroupListener
    • Fixed a problem when running the tests locally in a PowerShell console it
      would ask for parameters (issue #897).
  • Changes to xSQLServerMaxDop
    • Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
      the resource will only determine if a change is needed if the target node
      is the active host of the SQL Server instance (issue #882).

v8.2.0

25 Dec 09:13
Compare
Choose a tag to compare
  • Changes to xSQLServer
    • Updated appveyor.yml so that integration tests run in order and so that
      the SQLPS module folders are renamed to not disturb the units test, but
      can be renamed back by the integration tests xSQLServerSetup so that the
      integration tests can run successfully
      (issue #774).
    • Changed so the maximum version to be installed is 4.0.6.0, when running unit
      tests in AppVeyor. Quick fix until we can resolve the unit tests (see
      issue #807).
    • Moved the code block, that contains workarounds in appveyor.yml, so it is run
      during the install phase instead of the test phase.
    • Fix problem with tests breaking with Pester 4.0.7 (issue #807).
  • Changes to xSQLServerHelper
    • Changes to Connect-SQL and Import-SQLPSModule
      • Now it correctly loads the correct assemblies when SqlServer module is
        present (issue #649).
      • Now SQLPS module will be correctly loaded (discovered) after installation
        of SQL Server. Previously resources depending on SQLPS module could fail
        because SQLPS was not found after installation because the PSModulePath
        environment variable in the (LCM) PowerShell session did not contain the new
        module path.
    • Added new helper function "Test-ClusterPermissions" (issue #446).
  • Changes to xSQLServerSetup
    • Fixed an issue with trailing slashes in the 'UpdateSource' property
      (issue #720).
    • Fixed so that the integration test renames back the SQLPS module folders if
      they was renamed by AppVeyor (in the appveyor.yml file)
      (issue #774).
    • Fixed so integration test does not write warnings when SQLPS module is loaded
      (issue #798).
    • Changes to integration tests.
      • Moved the configuration block from the MSFT_xSQLServerSetup.Integration.Tests.ps1
        to the MSFT_xSQLServerSetup.config.ps1 to align with the other integration
        test. And also get most of the configuration in one place.
      • Changed the tests so that the local SqlInstall account is added as a member
        of the local administrators group.
      • Changed the tests so that the local SqlInstall account is added as a member
        of the system administrators in SQL Server (Database Engine) - needed for the
        xSQLServerAlwaysOnService integration tests.
      • Changed so that only one of the Modules-folder for the SQLPS PowerShell module
        for SQL Server 2016 is renamed back so it can be used with the integration
        tests. There was an issue when more than one SQLPS module was present (see
        more information in issue #806).
      • Fixed wrong variable name for SQL service credential. It was using the
        integration test variable name instead of the parameter name.
      • Added ErrorAction 'Stop' to the cmdlet Start-DscConfiguration
        (issue #824).
  • Changes to xSQLServerAlwaysOnAvailabilityGroup
    • Change the check of the values entered as parameter for
      BasicAvailabilityGroup. It is a boolean, hence it was not possible to
      disable the feature.
    • Add possibility to enable/disable the feature DatabaseHealthTrigger
      (SQL Server 2016 or later only).
    • Add possibility to enable the feature DtcSupportEnabled (SQL Server 2016 or
      later only). The feature currently can't be altered once the Availability
      Group is created.
    • Use the new helper function "Test-ClusterPermissions".
    • Refactored the unit tests to allow them to be more user friendly.
    • Added the following read-only properties to the schema (issue #476)
      • EndpointPort
      • EndpointURL
      • SQLServerNetName
      • Version
    • Use the Get-PrimaryReplicaServerObject helper function.
  • Changes to xSQLServerAlwaysOnAvailabilityGroupReplica
    • Fixed the formatting for the AvailabilityGroupNotFound error.
    • Added the following read-only properties to the schema (issue #477)
      • EndpointPort
      • EndpointURL
    • Use the new helper function "Test-ClusterPermissions".
    • Use the Get-PrimaryReplicaServerObject helper function
  • Changes to xSQLServerHelper
    • Fixed Connect-SQL by ensuring the Status property returns 'Online' prior to
      returning the SQL Server object (issue #333).
  • Changes to xSQLServerRole
    • Running Get-DscConfiguration no longer throws an error saying property
      Members is not an array (issue #790).
  • Changes to xSQLServerMaxDop
    • Fixed error where Measure-Object cmdlet would fail claiming it could not
      find the specified property (issue #801)
  • Changes to xSQLServerAlwaysOnService
    • Added integration test (issue #736).
      • Added ErrorAction 'Stop' to the cmdlet Start-DscConfiguration
        (issue #824).
  • Changes to SMO.cs
    • Added default properties to the Server class
      • AvailabilityGroups
      • Databases
      • EndpointCollection
    • Added a new overload to the Login class
    • Added default properties to the AvailabilityReplicas class
      • AvailabilityDatabases
      • AvailabilityReplicas
  • Added new resource xSQLServerAccount (issue #706)
    • Added localization support for all strings
    • Added examples for usage
  • Changes to xSQLServerRSConfig
    • No longer returns a null value from Test-TargetResource when Reporting
      Services has not been initialized (issue #822).
    • Fixed so that when two Reporting Services are installed for the same major
      version the resource does not throw an error (issue #819).
    • Now the resource will restart the Reporting Services service after
      initializing (issue #592).
      This will enable the Reports site to work.
    • Added integration test (issue #753).
    • Added support for configuring URL reservations and virtual directory names
      (issue #570)
  • Added resource

v8.1.0

25 Dec 09:11
Compare
Choose a tag to compare
  • Changes to xSQLServer
    • Added back .markdownlint.json so that lint rule MD013 is enforced.
    • Change the module to use the image 'Visual Studio 2017' as the build worker
      image for AppVeyor (issue #685).
    • Minor style change in CommonResourceHelper. Added missing [Parameter()] on
      three parameters.
    • Minor style changes to the unit tests for CommonResourceHelper.
    • Changes to xSQLServerHelper
    • Opt-in for module files common tests (issue #702).
      • Removed Byte Order Mark (BOM) from the files; CommonResourceHelper.psm1,
        MSFT_xSQLServerAvailabilityGroupListener.psm1, MSFT_xSQLServerConfiguration.psm1,
        MSFT_xSQLServerEndpointPermission.psm1, MSFT_xSQLServerEndpointState.psm1,
        MSFT_xSQLServerNetwork.psm1, MSFT_xSQLServerPermission.psm1,
        MSFT_xSQLServerReplication.psm1, MSFT_xSQLServerScript.psm1,
        SQLPSStub.psm1, SQLServerStub.psm1.
    • Opt-in for script files common tests (issue #707).
      • Removed Byte Order Mark (BOM) from the files; DSCClusterSqlBuild.ps1,
        DSCFCISqlBuild.ps1, DSCSqlBuild.ps1, DSCSQLBuildEncrypted.ps1,
        SQLPush_SingleServer.ps1, 1-AddAvailabilityGroupListenerWithSameNameAsVCO.ps1,
        2-AddAvailabilityGroupListenerWithDifferentNameAsVCO.ps1,
        3-RemoveAvailabilityGroupListenerWithSameNameAsVCO.ps1,
        4-RemoveAvailabilityGroupListenerWithDifferentNameAsVCO.ps1,
        5-AddAvailabilityGroupListenerUsingDHCPWithDefaultServerSubnet.ps1,
        6-AddAvailabilityGroupListenerUsingDHCPWithSpecificSubnet.ps1,
        2-ConfigureInstanceToEnablePriorityBoost.ps1, 1-CreateEndpointWithDefaultValues.ps1,
        2-CreateEndpointWithSpecificPortAndIPAddress.ps1, 3-RemoveEndpoint.ps1,
        1-AddConnectPermission.ps1, 2-RemoveConnectPermission.ps1,
        3-AddConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1,
        4-RemoveConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1,
        1-MakeSureEndpointIsStarted.ps1, 2-MakeSureEndpointIsStopped.ps1,
        1-EnableTcpIpWithStaticPort.ps1, 2-EnableTcpIpWithDynamicPort.ps1,
        1-AddServerPermissionForLogin.ps1, 2-RemoveServerPermissionForLogin.ps1,
        1-ConfigureInstanceAsDistributor.ps1, 2-ConfigureInstanceAsPublisher.ps1,
        1-WaitForASingleClusterGroup.ps1, 2-WaitForMultipleClusterGroups.ps1.
    • Updated year to 2017 in license file (issue #711).
    • Code style clean-up throughout the module to align against the Style Guideline.
    • Fixed typos and the use of wrong parameters in unit tests which was found
      after release of new version of Pester (issue #773).
  • Changes to xSQLServerAlwaysOnService
    • Added resource description in README.md.
    • Updated parameters descriptions in comment-based help, schema.mof and README.md.
    • Changed the datatype of the parameter to UInt32 so the same datatype is used
      in both the Get-/Test-/Set-TargetResource functions as in the schema.mof
      (issue #688).
    • Added read-only property IsHadrEnabled to schema.mof and the README.md
      (issue #687).
    • Minor cleanup of code.
    • Added examples (issue #633)
      • 1-EnableAlwaysOn.ps1
      • 2-DisableAlwaysOn.ps1
    • Fixed PS Script Analyzer errors (issue #724)
    • Casting the result of the property IsHadrEnabled to [System.Boolean] so that
      $null is never returned, which resulted in an exception (issue #763).
  • Changes to xSQLServerDatabasePermission
  • Changes to xSQLServerScript
  • Changes to xSQLServerSetup
    • Added Swedish localization (issue #695).
    • Now Get-TargetResource correctly returns an array for property ASSysAdminAccounts,
      and no longer throws an error when there is just one Analysis Services
      administrator (issue #691).
    • Added a simple integration test (issue #709).
    • Fixed PS Script Analyzer errors (issue #729)

v8.0.0

25 Dec 09:10
Compare
Choose a tag to compare
  • BREAKING CHANGE: The module now requires WMF 5.
    • This is required for class-based resources
  • Added new resource
    • xSQLServerAlwaysOnAvailabilityGroupDatabaseMembership
    • Added localization support for all strings.
    • Refactored as a MOF based resource due to challenges with Pester and testing
      in Powershell 5.
  • Changes to xSQLServer
    • BREAKING CHANGE: xSQLServer does no longer try to support WMF 4.0 (PowerShell
      4.0) (issue #574). Minimum supported version of WMF is now 5.0 (PowerShell 5.0).
    • BREAKING CHANGE: Removed deprecated resource xSQLAOGroupJoin (issue #457).
    • BREAKING CHANGE: Removed deprecated resource xSQLAOGroupEnsure (issue #456).
    • BREAKING CHANGE: Removed deprecated resource xSQLServerFailoverClusterSetup
      (issue #336).
    • Updated PULL_REQUEST_TEMPLATE adding comment block around text. Also
      rearranged and updated texts (issue #572).
    • Added common helper functions for HQRM localization, and added tests for the
      helper functions.
      • Get-LocalizedData
      • New-InvalidResultException
      • New-ObjectNotFoundException
      • New-InvalidOperationException
      • New-InvalidArgumentException
    • Updated CONTRIBUTING.md describing the new localization helper functions.
    • Fixed typos in xSQLServer.strings.psd1
    • Fixed CodeCov badge links in README.md so that they point to the correct branch.
    • Added VS Code workspace settings file with formatting settings matching the
      Style Guideline (issue #645). That will make it possible inside VS Code to press
      SHIFT+ALT+F, or press F1 and choose 'Format document' in the list. The
      PowerShell code will then be formatted according to the Style Guideline
      (although maybe not complete, but would help a long way).
      • Removed powershell.codeFormatting.alignPropertyValuePairs setting since
        it does not align with the style guideline.
      • Added powershell.codeFormatting.preset with a value of 'Custom' so that
        workspace formatting settings are honored (issue #665).
    • Fixed lint error MD013 and MD036 in README.md.
    • Updated .markdownlint.json to enable rule MD013 and MD036 to enforce those
      lint markdown rules in the common tests.
    • Fixed lint error MD013 in CHANGELOG.md.
    • Fixed lint error MD013 in CONTRIBUTING.md.
    • Added code block around types in README.md.
    • Updated copyright information in xSQLServer.psd1.
    • Opt-in for markdown common tests (issue #668).
      • The old markdown tests has been removed.
  • Changes to xSQLServerHelper
    • Removed helper function Grant-ServerPerms because the deprecated resource that
      was using it was removed.
    • Removed helper function Grant-CNOPerms because the deprecated resource that
      was using it was removed.
    • Removed helper function New-ListenerADObject because the deprecated resource
      that was using it was removed.
    • Added tests for those helper functions that did not have tests.
    • Test-SQLDscParameterState helper function can now correctly pass a CimInstance
      as DesiredValue.
    • Test-SQLDscParameterState helper function will now output a warning message
      if the value type of a desired value is not supported.
    • Added localization to helper functions (issue #641).
      • Resolved the issue when using Write-Verbose in helper functions discussed
        in #641 where Write-Verbose wouldn't write out verbose messages unless using
        parameter Verbose.
      • Moved localization strings from xSQLServer.strings.psd1 to
        xSQLServerHelper.strings.psd1.
  • Changes to xSQLServerSetup
    • BREAKING CHANGE: Replaced StartWin32Process helper function with the cmdlet
      Start-Process (issue #41, #93 and #126).
    • BREAKING CHANGE: The parameter SetupCredential has been removed since it is
      no longer needed. This is because the resource now support the built-in
      PsDscRunAsCredential.
    • BREAKING CHANGE: Now the resource supports using built-in PsDscRunAsCredential.
      If PsDscRunAsCredential is set, that username will be used as the first system
      administrator.
    • BREAKING CHANGE: If the parameter PsDscRunAsCredential are not assigned any
      credentials then the resource will start the setup process as the SYSTEM account.
      When installing as the SYSTEM account, then parameter SQLSysAdminAccounts and
      ASSysAdminAccounts must be specified when installing feature Database Engine
      and Analysis Services respectively.
    • When setup exits with the exit code 3010 a warning message is written to console
      telling that setup finished successfully, but a reboot is required (partly fixes
      issue #565).
    • When setup exits with an exit code other than 0 or 3010 a warning message is
      written to console telling that setup finished with an error (partly fixes
      issue #580).
    • Added a new parameter SetupProcessTimeout which defaults to 7200 seconds (2
      hours). If the setup process has not finished before the timeout value in
      SetupProcessTimeout an error will be thrown (issue #566).
    • Updated all examples to match the removal of SetupCredential.
    • Updated (removed) severe known issues in README.md for resource xSQLServerSetup.
    • Now all major version uses the same identifier to evaluate InstallSharedDir
      and InstallSharedWOWDir (issue #420).
    • Now setup arguments that contain no value will be ignored, for example when
      InstallSharedDir and
      InstallSharedWOWDir path is already present on the target node, because of a
      previous installation (issue #639).
    • Updated Get-TargetResource to correctly detect BOL, Conn, BC and other tools
      when they are installed without SQLENGINE (issue #591).
    • Now it can detect Documentation Components correctly after the change in
      issue #591 (issue #628)
    • Fixed bug that prevented Get-DscConfiguration from running without error. The
      return hash table fails if the $clusteredSqlIpAddress variable is not used.
      The schema expects a string array but it is initialized as just a null string,
      causing it to fail on Get-DscConfiguration (issue #393).
    • Added localization support for all strings.
    • Added a test to test some error handling for cluster installations.
    • Added support for MDS feature install (issue #486)
      • Fixed localization support for MDS feature (issue #671).
  • Changes to xSQLServerRSConfig
    • BREAKING CHANGE: Removed $SQLAdminCredential parameter. Use common parameter
      PsDscRunAsCredential (WMF 5.0+) to run the resource under different credentials.
      PsDscRunAsCredential Windows account must be a sysadmin on SQL Server (issue
      #568).
    • In addition, the resource no longer uses Invoke-Command cmdlet that was used
      to impersonate the Windows user specified by $SQLAdminCredential. The call
      also needed CredSSP authentication to be enabled and configured on the target
      node, which complicated deployments in non-domain scenarios. Using
      PsDscRunAsCredential solves this problems for us.
    • Fixed virtual directory creation for SQL Server 2016 (issue #569).
    • Added unit tests (issue #295).
  • Changes to xSQLServerDatabase
    • Changed the readme, SQLInstance should have been SQLInstanceName.
  • Changes to xSQLServerScript
    • Fixed bug with schema and variable mismatch for the Credential/Username parameter
      in the return statement (issue #661).
    • Optional QueryTimeout parameter to specify sql script query execution timeout.
      Fixes issue #597
  • Changes to xSQLServerAlwaysOnService
    • Fixed typos in localization strings and in tests.
  • Changes to xSQLServerAlwaysOnAvailabilityGroup
    • Now it utilize the value of 'FailoverMode' to set the 'FailoverMode' property
      of the Availability Group instead of wrongly using the 'AvailabilityMode'
      property of the Availability Group.

v7.1.0

25 Dec 09:10
Compare
Choose a tag to compare
  • Changes to xSQLServerMemory
    • Changed the way SQLServer parameter is passed from Test-TargetResource to
      Get-TargetResource so that the default value isn't lost (issue #576).
    • Added condition to unit tests for when no SQLServer parameter is set.
  • Changes to xSQLServerMaxDop
    • Changed the way SQLServer parameter is passed from Test-TargetResource to
      Get-TargetResource so that the default value isn't lost (issue #576).
    • Added condition to unit tests for when no SQLServer parameter is set.
  • Changes to xWaitForAvailabilityGroup
    • Updated README.md with a description for the resources and revised the parameter
      descriptions.
    • The default value for RetryIntervalSec is now 20 seconds and the default value
      for RetryCount is now 30 times (issue #505).
    • Cleaned up code and fixed PSSA rules warnings (issue #268).
    • Added unit tests (issue #297).
    • Added descriptive text to README.md that the account that runs the resource
      must have permission to run the cmdlet Get-ClusterGroup (issue #307).
    • Added read-only parameter GroupExist which will return $true if the cluster
      role/group exist, otherwise it returns $false (issue #510).
    • Added examples.
  • Changes to xSQLServerPermission
    • Cleaned up code, removed SupportsShouldProcess and fixed PSSA rules warnings
      (issue #241 and issue #262).
    • It is now possible to add permissions to two or more logins on the same instance
      (issue #526).
    • The parameter NodeName is no longer mandatory and has now the default value
      of $env:COMPUTERNAME.
    • The parameter Ensure now has a default value of 'Present'.
    • Updated README.md with a description for the resources and revised the parameter
      descriptions.
    • Removed dependency of SQLPS provider (issue #482).
    • Added ConnectSql permission. Now that permission can also be granted or revoked.
    • Updated note in resource description to also mention ConnectSql permission.
  • Changes to xSQLServerHelper module
    • Removed helper function Get-SQLPSInstance and Get-SQLPSInstanceName because
      there is no resource using it any longer.
    • Added four new helper functions.
      • Register-SqlSmo, Register-SqlWmiManagement and Unregister-SqlAssemblies to
        handle the creation on the application domain and loading and unloading of
        the SMO and SqlWmiManagement assemblies.
      • Get-SqlInstanceMajorVersion to get the major SQL version for a specific instance.
    • Fixed typos in comment-based help
  • Changes to xSQLServer
    • Fixed typos in markdown files; CHANGELOG, CONTRIBUTING, README and ISSUE_TEMPLATE.
    • Fixed typos in schema.mof files (and README.md).
    • Updated some parameter description in schema.mof files on those that was found
      was not equal to README.md.
  • Changes to xSQLServerAlwaysOnService
    • Get-TargetResource should no longer fail silently with error 'Index operation
      failed; the array index evaluated to null.' (issue #519). Now if the
      Server.IsHadrEnabled property return neither $true or $false the
      Get-TargetResource function will throw an error.
  • Changes to xSQLServerSetUp
    • Updated xSQLServerSetup Module Get-Resource method to fix (issue #516 and #490).
    • Added change to detect DQ, DQC, BOL, SDK features. Now the function
      Test-TargetResource returns true after calling set for DQ, DQC, BOL, SDK
      features (issue #516 and #490).
  • Changes to xSQLServerAlwaysOnAvailabilityGroup
    • Updated to return the exception raised when an error is thrown.
  • Changes to xSQLServerAlwaysOnAvailabilityGroupReplica
    • Updated to return the exception raised when an error is thrown.
    • Updated parameter description for parameter Name, so that it says it must be
      in the format SQLServer\InstanceName for named instance (issue #548).
  • Changes to xSQLServerLogin
    • Added an optional boolean parameter Disabled. It can be used to enable/disable
      existing logins or create disabled logins (new logins are created as enabled
      by default).
  • Changes to xSQLServerDatabaseRole
    • Updated variable passed to Microsoft.SqlServer.Management.Smo.User constructor
      to fix issue #530
  • Changes to xSQLServerNetwork
    • Added optional parameter SQLServer with default value of $env:COMPUTERNAME
      (issue #528).
    • Added optional parameter RestartTimeout with default value of 120 seconds.
    • Now the resource supports restarting a sql server in a cluster (issue #527
      and issue #455).
    • Now the resource allows to set the parameter TcpDynamicPorts to a blank value
      (partly fixes issue #534). Setting a blank value for parameter TcpDynamicPorts
      together with a value for parameter TcpPort means that static port will be used.
    • Now the resource will not call Alter() in the Set-TargetResource when there
      is no change necessary (issue #537).
    • Updated example 1-EnableTcpIpOnCustomStaticPort.
    • Added unit tests (issue #294).
    • Refactored some of the code, cleaned up the rest and fixed PSSA rules warnings
      (issue #261).
    • If parameter TcpDynamicPort is set to '0' at the same time as TcpPort is set
      the resource will now throw an error (issue #535).
    • Added examples (issue #536).
    • When TcpDynamicPorts is set to '0' the Test-TargetResource function will no
      longer fail each time (issue #564).
  • Changes to xSQLServerRSConfig
    • Replaced sqlcmd.exe usages with Invoke-Sqlcmd calls (issue #567).
  • Changes to xSQLServerDatabasePermission
    • Fixed code style, updated README.md and removed *-SqlDatabasePermission functions
      from xSQLServerHelper.psm1.
    • Added the option 'GrantWithGrant' with gives the user grant rights, together
      with the ability to grant others the same right.
    • Now the resource can revoke permission correctly (issue #454). When revoking
      'GrantWithGrant', both the grantee and all the other users the grantee has
      granted the same permission to, will also get their permission revoked.
    • Updated tests to cover Revoke().
  • Changes to xSQLServerHelper
    • The missing helper function ('Test-SPDSCObjectHasProperty'), that was referenced
      in the helper function Test-SQLDscParameterState, is now incorporated into
      Test-SQLDscParameterState (issue #589).

v7.0.0

25 Dec 09:05
Compare
Choose a tag to compare
  • Examples
    • xSQLServerDatabaseRole
      • 1-AddDatabaseRole.ps1
      • 2-RemoveDatabaseRole.ps1
    • xSQLServerRole
      • 3-AddMembersToServerRole.ps1
      • 4-MembersToIncludeInServerRole.ps1
      • 5-MembersToExcludeInServerRole.ps1
    • xSQLServerSetup
      • 1-InstallDefaultInstanceSingleServer.ps1
      • 2-InstallNamedInstanceSingleServer.ps1
      • 3-InstallNamedInstanceSingleServerFromUncPathUsingSourceCredential.ps1
      • 4-InstallNamedInstanceInFailoverClusterFirstNode.ps1
      • 5-InstallNamedInstanceInFailoverClusterSecondNode.ps1
    • xSQLServerReplication
      • 1-ConfigureInstanceAsDistributor.ps1
      • 2-ConfigureInstanceAsPublisher.ps1
    • xSQLServerNetwork
      • 1-EnableTcpIpOnCustomStaticPort.ps1
    • xSQLServerAvailabilityGroupListener
      • 1-AddAvailabilityGroupListenerWithSameNameAsVCO.ps1
      • 2-AddAvailabilityGroupListenerWithDifferentNameAsVCO.ps1
      • 3-RemoveAvailabilityGroupListenerWithSameNameAsVCO.ps1
      • 4-RemoveAvailabilityGroupListenerWithDifferentNameAsVCO.ps1
      • 5-AddAvailabilityGroupListenerUsingDHCPWithDefaultServerSubnet.ps1
      • 6-AddAvailabilityGroupListenerUsingDHCPWithSpecificSubnet.ps1
    • xSQLServerEndpointPermission
      • 1-AddConnectPermission.ps1
      • 2-RemoveConnectPermission.ps1
      • 3-AddConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1
      • 4-RemoveConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1
    • xSQLServerPermission
      • 1-AddServerPermissionForLogin.ps1
      • 2-RemoveServerPermissionForLogin.ps1
    • xSQLServerEndpointState
      • 1-MakeSureEndpointIsStarted.ps1
      • 2-MakeSureEndpointIsStopped.ps1
    • xSQLServerConfiguration
      • 1-ConfigureTwoInstancesOnTheSameServerToEnableClr.ps1
      • 2-ConfigureInstanceToEnablePriorityBoost.ps1
    • xSQLServerEndpoint
      • 1-CreateEndpointWithDefaultValues.ps1
      • 2-CreateEndpointWithSpecificPortAndIPAddress.ps1
      • 3-RemoveEndpoint.ps1
  • Changes to xSQLServerDatabaseRole
    • Fixed code style, added updated parameter descriptions to schema.mof and README.md.
  • Changes to xSQLServer
    • Raised the CodeCov target to 70% which is the minimum and required target for
      HQRM resource.
  • Changes to xSQLServerRole
    • BREAKING CHANGE: The resource has been reworked in it's entirely. Below
      is what has changed.
      • The mandatory parameters now also include ServerRoleName.
      • The ServerRole parameter was before an array of server roles, now this parameter
        is renamed to ServerRoleName and can only be set to one server role.
        • ServerRoleName are no longer limited to built-in server roles. To add members
          to a built-in server role, set ServerRoleName to the name of the built-in
          server role.
        • The ServerRoleName will be created when Ensure is set to 'Present' (if it
          does not already exist), or removed if Ensure is set to 'Absent'.
      • Three new parameters are added; Members, MembersToInclude and MembersToExclude.
        • Members can be set to one or more logins, and those will replace all the
          memberships in the server role.
        • MembersToInclude and MembersToExclude can be set to one or more logins that
          will add or remove memberships, respectively, in the server role. MembersToInclude
          and MembersToExclude can not be used at the same time as parameter Members.
          But both MembersToInclude and MembersToExclude can be used together at the
          same time.
  • Changes to xSQLServerSetup
    • Added a note to the README.md saying that it is not possible to add or remove
      features from a SQL Server failover cluster (issue #433).
    • Changed so that it reports false if the desired state is not correct (issue #432).
      • Added a test to make sure we always return false if a SQL Server failover
        cluster is missing features.
    • Helper function Connect-SQLAnalysis
      • Now has correct error handling, and throw does not used the unknown named
        parameter '-Message' (issue #436)
      • Added tests for Connect-SQLAnalysis
      • Changed to localized error messages.
      • Minor changes to error handling.
    • This adds better support for Addnode (issue #369).
    • Now it skips cluster validation för add node (issue #442).
    • Now it ignores parameters that are not allowed for action Addnode (issue #441).
    • Added support for vNext CTP 1.4 (issue #472).
  • Added new resource
    • xSQLServerAlwaysOnAvailabilityGroupReplica
  • Changes to xSQLServerDatabaseRecoveryModel
    • Fixed code style, removed SQLServerDatabaseRecoveryModel functions from xSQLServerHelper.
  • Changes to xSQLServerAlwaysOnAvailabilityGroup
    • Fixed the permissions check loop so that it exits the loop after the function
      determines the required permissions are in place.
  • Changes to xSQLServerAvailabilityGroupListener
    • Removed the dependency of SQLPS provider (issue #460).
    • Cleaned up code.
    • Added test for more coverage.
    • Fixed PSSA rule warnings (issue #255).
    • Parameter Ensure now defaults to 'Present' (issue #450).
  • Changes to xSQLServerFirewall
    • Now it will correctly create rules when the resource is used for two or more
      instances on the same server (issue #461).
  • Changes to xSQLServerEndpointPermission
    • Added description to the README.md
    • Cleaned up code (issue #257 and issue #231)
    • Now the default value for Ensure is 'Present'.
    • Removed dependency of SQLPS provider (issue #483).
    • Refactored tests so they use less code.
  • Changes to README.md
    • Adding deprecated tag to xSQLServerFailoverClusterSetup, xSQLAOGroupEnsure and
      xSQLAOGroupJoin in README.md so it it more clear that these resources has been
      replaced by xSQLServerSetup, xSQLServerAlwaysOnAvailabilityGroup and
      xSQLServerAlwaysOnAvailabilityGroupReplica respectively.
  • Changes to xSQLServerEndpoint
    • BREAKING CHANGE: Now SQLInstanceName is mandatory, and is a key, so
      SQLInstanceName has no longer a default value (issue #279).
    • BREAKING CHANGE: Parameter AuthorizedUser has been removed (issue #466,
      issue #275 and issue #80). Connect permissions can be set using the resource
      xSQLServerEndpointPermission.
    • Optional parameter IpAddress has been added. Default is to listen on any
      valid IP-address. (issue #232)
    • Parameter Port now has a default value of 5022.
    • Parameter Ensure now defaults to 'Present'.
    • Resource now supports changing IP address and changing port.
    • Added unit tests (issue #289)
    • Added examples.
  • Changes to xSQLServerEndpointState
    • Cleaned up code, removed SupportsShouldProcess and fixed PSSA rules warnings
      (issue #258 and issue #230).
    • Now the default value for the parameter State is 'Started'.
    • Updated README.md with a description for the resources and revised the
      parameter descriptions.
    • Removed dependency of SQLPS provider (issue #481).
    • The parameter NodeName is no longer mandatory and has now the default value
      of $env:COMPUTERNAME.
    • The parameter Name is now a key so it is now possible to change the state on
      more than one endpoint on the same instance. Note: The resource still only
      supports Database Mirror endpoints at this time.
  • Changes to xSQLServerHelper module
    • Removing helper function Get-SQLAlwaysOnEndpoint because there is no resource
      using it any longer.
    • BREAKING CHANGE: Changed helper function Import-SQLPSModule to support SqlServer
      module (issue #91). The SqlServer module is the preferred module so if it is
      found it will be used, and if not found an attempt will be done to load SQLPS
      module instead.
  • Changes to xSQLServerScript
    • Updated tests for this resource, because they failed when Import-SQLPSModule
      was updated.

v6.0.0

25 Dec 09:04
Compare
Choose a tag to compare
  • Changes to xSQLServerConfiguration
    • BREAKING CHANGE: The parameter SQLInstanceName is now mandatory.
    • Resource can now be used to define the configuration of two or more different
      DB instances on the same server.
  • Changes to xSQLServerRole
    • xSQLServerRole now correctly reports that the desired state is present when
      the login is already a member of the server roles.
  • Added new resources
    • xSQLServerAlwaysOnAvailabilityGroup
  • Changes to xSQLServerSetup
    • Properly checks for use of SQLSysAdminAccounts parameter in $PSBoundParameters.
      The test now also properly evaluates the setup argument for SQLSysAdminAccounts.
    • xSQLServerSetup should now function correctly for the InstallFailoverCluster
      action, and also supports cluster shared volumes. Note that the AddNode action
      is not currently working.
    • It now detects that feature Client Connectivity Tools (CONN) and Client
      Connectivity Backwards Compatibility Tools (BC) is installed.
    • Now it can correctly determine the right cluster when only parameter
      InstallSQLDataDir is assigned a path (issue #401).
    • Now the only mandatory path parameter is InstallSQLDataDir when installing
      Database Engine (issue #400).
    • It now can handle mandatory parameters, and are not using wildcard to find
      the variables containing paths (issue #394).
    • Changed so that instead of connection to localhost it is using $env:COMPUTERNAME
      as the host name to which it connects. And for cluster installation it uses
      the parameter FailoverClusterNetworkName as the host name to which it connects
      (issue #407).
    • When called with Action = 'PrepareFailoverCluster', the SQLSysAdminAccounts
      and FailoverClusterGroup parameters are no longer passed to the setup process
      (issues #410 and 411).
    • Solved the problem that InstanceDir and InstallSQLDataDir could not be set to
      just a qualifier, i.e 'E:' (issue #418). All paths (except SourcePath) can now
      be set to just the qualifier.
  • Enables CodeCov.io code coverage reporting.
  • Added badge for CodeCov.io to README.md.
  • Examples
    • xSQLServerMaxDop
      • 1-SetMaxDopToOne.ps1
      • 2-SetMaxDopToAuto.ps1
      • 3-SetMaxDopToDefault.ps1
    • xSQLServerMemory
      • 1-SetMaxMemoryTo12GB.ps1
      • 2-SetMaxMemoryToAuto.ps1
      • 3-SetMinMaxMemoryToAuto.ps1
      • 4-SetMaxMemoryToDefault.ps1
    • xSQLServerDatabase
      • 1-CreateDatabase.ps1
      • 2-DeleteDatabase.ps1
  • Added tests for resources
    • xSQLServerMaxDop
    • xSQLServerMemory
  • Changes to xSQLServerMemory
    • BREAKING CHANGE: The mandatory parameter now include SQLInstanceName. The
      DynamicAlloc parameter is no longer mandatory
  • Changes to xSQLServerDatabase
    • When the system is not in desired state the Test-TargetResource will now output
      verbose messages saying so.
  • Changes to xSQLServerDatabaseOwner
    • Fixed code style, added updated parameter descriptions to schema.mof and README.md.