Download

Releases

Please see the SQLDSC: What’s New for details.

Update license file location
Queries support multiple directories. Please see the docs.
Executing queries no longer requires the .sql extension allowing a shorter syntax. For example, sqldsc query db_count runs db_count.sql.

A login resource block for sa defaults to alter so we don’t try to create the sa login in an Azure SQL Database.
A database resource block for model defaults to alter so we don’t try to create the model database in an Azure SQL Database.
agent_job now defaults to being owned by sa if not specified on creation. This seems like a more reasonable default.

Add proxy server support
PRO Edition licensing now comes from the SQLDSC Portal
The PRO Edition includes beta support for running a raw SELECT query against each target

BREAKING CHANGE: How roles are processed has changed. Please see PRO: Roles.
Roles now support nesting. This allows a role to include additional roles. For example, an Availibility Group role can include all the needed roles rather than defining them for each node.
login blocks allow a default_schema to be set for database and user_databases blocks
sqldsc list lists all the targets and their roles after applying filters
Early support for case-sensitive servers and databases
Added for_versions filter for resource blocks. Please see PRO: Filter for Versions for details.
New databases default to being owned by sa unless an owner is specified
Job schedules can now have their start time “jittered” so they don’t all start at the same time. Please see Agent Resource Blocks
database resource blocks can now set the database compatibility level. A value of -1 matches the server version.
Logging SQL statements now captures the database name
Improved handling of EXEC vs. EXECUTE in GRANT statements
SSISDB is considered a system database (i.e. NOT a user database)

Resource blocks now merge instead of overwriting previous blocks. Please see Resource Block Precendence
Added user_databases blocks to the PRO Edition
Added login blocks to the PRO Edition
Added variables to the PRO Edition
BREAKING: Changed how roles are processed
BREAKING: Changed server role members and server permissions
Added support for schemas and schema permissions

Start support for Azure “SQL Databases”.
Added limited support for SQL Server Agent Jobs.
Added support for Database Roles.
The application logging format has changed to make it easier to read.
Targets support SQL Server logins.
Targets can define roles which override the default Roles or added_roles which add to the default Roles.
Both test and apply stop processing on errors. Originally they would stop the current target but process other targets. However the safest action is to stop immediately if there’s a problem. If the test is running multi-threaded, each thread will finish its target but won’t start new a one.
Testing a password in the Vault can test both passwords and password hashes.

New documentation site at docs.sqldsc.com
Added a --parallel flag for the PRO. This sets the number of testing threads equal to the number of targets. Applying is always done sequentially.
The application checks if a user is in the sysadmin role. If they are not, the target is skipped. This better supports running with two different accounts.
The PRO edition can configure the multi-threaded settings using a settings file. Please see the Application Settings section.
The application can update itself by running sqldsc update. If there is a newer version, it will prompt you to install it.
sqldsc init will create a .vscode directory with the suggested extensions.
Improved handling of SQL Server logins. See SQL Server Logins for details.
- Capture and reuse SIDs
- Store hashed passwords in the Credential Vault
- Get the SID and hashed password from an existing login
If a database isn’t writeable, any changes for that database are silently skipped.