We’ve been trying to set-up SQLdebugger for our sql server database instance on test environment. Our aim was to allow developers to debug sql procedures execution through VisualStudio. One of the requirements is to grant sysadmin role for the user. We created a dedicated sql user for this purpose and we pass its credetials when starting debugger but unfortunately it does not work. It appears that sql user is ignored by the debugger and it is windows user that is passed to DB that is missing sysadmin on the SQLServer (the same that runs VisualStudio).
In details here is what we do:
- First we run VisualStudio (2019, 2022 – it makes no difference) as a current windows user and prepare some script that runs a stored procedure on SqlServer. We run it using ‘Execute with debugger’ option
- SQl connecion dialog appears where w enter SqlServer user with sysadmin role on the SQL Server.
- After clicking ‘Connect’ following error appears:
We already checked that granting sysadmin role for the windows user that runs VisualStudio resolves the issue but this is not the way to go.
Do You have any idea if it is some bug in the debugger or the behaviour is as it should be? I do not get the purpose of displaying sql connection dialog if it is ignored eventually.
This question is not yet answered, be the first one who answer using the comment. Later the confirmed answer will be published as the solution.