You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Changes to SqlServerDsc
- New DSC resource SqlDatabaseUser (issue #846).
- Adds ability to create database users with more fine-grained control,
e.g. re-mapping of orphaned logins or a different login. Supports
creating a user with or without login name, and database users mapped
to a certificate or asymmetric key.
- Minor style fixes in unit tests.
- Changes to SqlDatabase
- Get-TargetResource now correctly return `$null` for the collation property
when the database does not exist (issue #1395).
- No longer enforces the collation property if the Collation parameter
is not part of the configuration (issue #1396).
- Updated resource description in README.md
- Fix examples to use `PsDscRunAsCredential` (issue #760).
- Added integration tests (issue #739).
- Updated unit tests to the latest template (issue #1068).
Details of the scenario you tried and the problem that is occurring:
This example should set
PsDscRunAsCredential
to $SysAdminAccount.https://github.com/PowerShell/xSQLServer/blob/dev/Examples/Resources/xSQLServerDatabase/1-CreateDatabase.ps1
The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
The text was updated successfully, but these errors were encountered: