You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How is it possible to run Invoke-DbaQuery function through Dedicated Admin Connection? I can't see no DedicatedAdminConnection switch in Invoke-DbaQuery documentation, like in other functions (for example Connect-DbaInstance).
With basic-role account (in VSCode debugging context, for example), the warning message is quite confusing because it does not tell us of any lack of privilege for running DAC in the first place, speaking of exhausted number of DAC connections instead 🤨
WARNING: [17:00:36][Connect-DbaInstance] Failed to open dedicated admin connection (DAC) to SVBOSSISDBT11\BOS. Only one DAC connection is allowed, so maybe another DAC is still open.
but is more meaningfull in the error message:
Error connecting to [server\instance]: Login failed for user 'Domain\MeAsBasicUser'
With sysadmin-role account (in [Domain\MeAsAdmin] account-elevated Windows Terminal console, for example), no more weird warning message, but I'am kicked out later in Invoke-DbaQuery with another blurry warning message:
WARNING: [17:06:12][Invoke-DbaQuery] Failure | Specified network name is no longer available
and the try/catch exception, because I'm trying to process the NULL resultset coming from faulty Invoke-DbaQuery
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
How is it possible to run
Invoke-DbaQuery
function through Dedicated Admin Connection? I can't see noDedicatedAdminConnection
switch inInvoke-DbaQuery
documentation, like in other functions (for exampleConnect-DbaInstance
).I tried to do the following:
and then
With basic-role account (in VSCode debugging context, for example), the warning message is quite confusing because it does not tell us of any lack of privilege for running DAC in the first place, speaking of exhausted number of DAC connections instead 🤨
but is more meaningfull in the error message:
With
sysadmin
-role account (in [Domain\MeAsAdmin] account-elevated Windows Terminal console, for example), no more weird warning message, but I'am kicked out later inInvoke-DbaQuery
with another blurry warning message:and the try/catch exception, because I'm trying to process the NULL resultset coming from faulty
Invoke-DbaQuery
Any idea of what I'm doing wrong?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions