Known Issues

[andreasjordan]

This is a list of known issues with dbatools

Please read this list before opening a new bug.

To see all open issues labeled as "known issue": known issue
To see all open isues labeled as "bugs life": bugs life

General issues and issues while importing the module

Using the SqlServer module together with dbatools

If you need to use both module in the same PowerShell session, it is very important to import the dbatools module first. So always use Import-Module -Name dbatools at the top of the script.

In case the SqlServer module is imported first, you might see the following error: Cannot convert the "System.Data.SqlClient.SqlConnection" value of type "System.Data.SqlClient.SqlConnection" to type "Microsoft.Data.SqlClient.SqlConnection"..

Using windows logins with the SqlCredential parameter

The parameter SqlCredential works best with sql logins. Using windows logins is also working in most cases, but the way the library is switching the security context has some limitations. On some systems we see the following error message: unable to load DLL 'Microsoft.Data.SqlClient.SNI.dll'. As a workaround try to start the PowerShell session under the desired windows login and then use integrated security. See #8268 for more details.

The import of dbatools is blocked by AV software like Defender or Carbon Black.

Sometimes the import is blocked and you get the following error message: This script contains malicious content and has been blocked by your antivirus software.. There is currently no way to fix this. See #8241 for more details.

Issues with specific commands

Invoke-DbaDbDataMasking

There are several known issues with this command:

• Invoke-DbaDbDataMasking not honoring "Persisted" property value on config file #7503
• Invoke-DbaDbDataMasking - Poor performance  #7940
• Invoke-DbaDbDataMasking - Leftovers when running datamasking #7941

Command 2