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
{{ message }}
This repository was archived by the owner on Feb 24, 2019. It is now read-only.
Do you want to request a feature or report a bug?
feature
What is the current behavior?
All data collection occurs using the same proxy account
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net
What is the expected behavior?
I would like to be able to specify a different connection credential for a specific instance. (If the credential does not exist then the Add-Dbr... command should create the credential & proxy combination and create alternative steps in the job to use that credential. The step should be intelligent enough to know not to pickup the servers that it's current credential does not have access to (something maybe [Security.Principal.WindowsIdentity]::GetCurrent().Name could help with this)
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
All supported
Do you want to request a feature or report a bug?
feature
What is the current behavior?
All data collection occurs using the same proxy account
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net
What is the expected behavior?
I would like to be able to specify a different connection credential for a specific instance. (If the credential does not exist then the Add-Dbr... command should create the credential & proxy combination and create alternative steps in the job to use that credential. The step should be intelligent enough to know not to pickup the servers that it's current credential does not have access to (something maybe [Security.Principal.WindowsIdentity]::GetCurrent().Name could help with this)
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
All supported