Dan Reist

Curious if any work has been done on this in the last two years? If not, I'd be willing to pick up on finishing this.

The workaround I found is this: `$serverObject = Connect-SQL -SQLServer $SQLServer -SQLInstanceName "$SQLInstanceName:1433"`

Went back to look at this today and discovered my installations of SQL are completely corrupt, so I have to re-install to continue investigating. I'll update then.

A working SQL instance makes all the difference :) Should we consider supporting a connection string (or something similar) for named instances when NamedPipes and the browser service are disabled,...

The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it...

To resolve this issue, a parameter called `ProcessOnlyOnActiveNode` should be created on the `Set-TargetResource` and `Test-TargetResource` functions. The `Get-TargetResource` function will execute the helper function `Test-ActiveNode` to determine if the...

The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it...

To resolve this issue, a parameter called `ProcessOnlyOnActiveNode` should be created on the `Set-TargetResource` and `Test-TargetResource` functions. The `Get-TargetResource` function will execute the helper function `Test-ActiveNode` to determine if the...

The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it...

To resolve this issue, a parameter called `ProcessOnlyOnActiveNode` should be created on the `Set-TargetResource` and `Test-TargetResource` functions. The `Get-TargetResource` function will execute the helper function `Test-ActiveNode` to determine if the...