I have found a couple of articles that look related. I can’t figure out how to build a connection string and pass that to invoke-dbaquery to test out what the links are suggesting. I use the MS SqlServer module in most of my tooling outside of Universal, I do not remember having an issue with it when connecting to the SQL server in my case. I will have to see if it has an issue if I use it within the dashboard.
I can reproduce this when using the integrated environment. The issue is that PowerShell Universal uses version 5.0 of the Microsoft.Data.SqlClient.dll. dbatools is using an older version of this DLL which is what is causing this issue.
When I run this outside of the integrated environment, I’m not seeing this issue. Can anyone else verify?
Typically, the slowest part of the system is the actual PowerShell execution so we typically don’t see issues with serialization slowing things down at all. We use protobuf and gRPC so it has really good throughput.