Options
Running Redgate source control as a different AD account
PBredgate
Posts: 1 New member
I have two activate directory accounts, one used for Database access "DB_Account" and another that is setup for DevOps "Std_Account" (This is how my work place's chosen setup).
This is causing issues when linking at database to source control, as SSMS is running as "DB_Account" it default to sign in to dev ops as this account which doesn't have a licence. The login in as another account is not work on the dev ops prompt, this loops and remains as the account running SSMS.
Is there an option to run the Red Gate extension /pop up in another account?
Currently as a work around I am saving committed changes to a shared folder location and then checking them into Dev Ops via visual studio. But I really want to just have one click Commits via SQL source control.
Any ever come across this before?
This is causing issues when linking at database to source control, as SSMS is running as "DB_Account" it default to sign in to dev ops as this account which doesn't have a licence. The login in as another account is not work on the dev ops prompt, this loops and remains as the account running SSMS.
Is there an option to run the Red Gate extension /pop up in another account?
Currently as a work around I am saving committed changes to a shared folder location and then checking them into Dev Ops via visual studio. But I really want to just have one click Commits via SQL source control.
Any ever come across this before?
Tagged:
Answers
Thanks for reaching out to us regarding this.
Unfortunately, there is currently no way to run SQL Source Control as any other user than the one used to connect to your instance in SSMS.
The workaround you are using might be the best one for now.
Dan Jary | Redgate Software
Have you visited our Help Center?