| Author | Ben Miller (@DBAduck) |
| Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Remove-DbaDbRole on GitHub.
Want to see the Bill Of Health for this command? Check out Remove-DbaDbRole.
Removes a database role from database(s) for each instance(s) of SQL Server.
The Remove-DbaDbRole removes role(s) from database(s) for each instance(s) of SQL Server.
Remove-DbaDbRole
[[-SqlInstance] <DbaInstanceParameter[]>]
[[-SqlCredential] <PSCredential>]
[[-Database] <String[]>]
[[-ExcludeDatabase] <String[]>]
[[-Role] <String[]>]
[[-ExcludeRole] <String[]>]
[-IncludeSystemDbs]
[[-InputObject] <Object[]>]
[-EnableException]
[-WhatIf]
[-Confirm]
[<CommonParameters>]
PS C:\> Remove-DbaDbRole -SqlInstance localhost -Database dbname -Role "customrole1", "customrole2"
Removes roles customrole1 and customrole2 from the database dbname on the local default SQL Server instance
PS C:\> Remove-DbaDbRole -SqlInstance localhost, sql2016 -Database db1, db2 -Role role1, role2, role3
Removes role1,role2,role3 from db1 and db2 on the local and sql2016 SQL Server instances
PS C:\> $servers = Get-Content C:\servers.txt
PS C:\> $servers | Remove-DbaDbRole -Database db1, db2 -Role role1
Removes role1 from db1 and db2 on the servers in C:\servers.txt
PS C:\> $roles = Get-DbaDbRole -SqlInstance localhost, sql2016 -Database db1, db2 -Role role1, role2, role3
PS C:\> $roles | Remove-DbaDbRole
Removes role1,role2,role3 from db1 and db2 on the local and sql2016 SQL Server instances
The target SQL Server instance or instances. This can be a collection and receive pipeline input to allow the function to be executed against multiple SQL Server instances.
| Alias | |
| Required | False |
| Pipeline | true (ByValue) |
| Default Value |
Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).
Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported.
For MFA support, please use Connect-DbaInstance.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
The database(s) to process. This list is auto-populated from the server. If unspecified, all databases will be processed.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
The database(s) to exclude. This list is auto-populated from the server.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
The role(s) to process. If unspecified, all roles will be processed.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
The role(s) to exclude.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
If this switch is enabled, roles can be removed from system databases.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | False |
Enables piped input from Get-DbaDbRole or Get-DbaDatabase
| Alias | |
| Required | False |
| Pipeline | true (ByValue) |
| Default Value |
By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | False |
Shows what would happen if the command were to run. No actions are actually performed.
| Alias | wi |
| Required | False |
| Pipeline | false |
| Default Value |
Prompts you for confirmation before executing any changing operations within the command.
| Alias | cf |
| Required | False |
| Pipeline | false |
| Default Value |