Comments
Sort by recent activity
I was able to get around this by specifying an AD group when it asked for the Administrator AD User. Since my AD Account is part of the group, I am able to log in. So instead of: me@domain.com I just typed the group name (with no domain prefix or suffix) and it worked. / comments
I was able to get around this by specifying an AD group when it asked for the Administrator AD User. Since my AD Account is part of the group, I am able to log in.So instead of:me@domain.com I ju...
I just downloaded the SQL ToolBelt from that link and it is listing 9.1 in the installer / comments
I just downloaded the SQL ToolBelt from that link and it is listing 9.1 in the installer
The only other issue is that it keeps throwing license errors. We only have one license - so limited to monitoring 5 databases. We have a lot more databases on that server. You select which five you want to monitor - but there is no way to tell it to ignore the other db's. Every morning I have to dismiss the errors and all the others show up in all the lists. / comments
The only other issue is that it keeps throwing license errors. We only have one license - so limited to monitoring 5 databases. We have a lot more databases on that server. You select which fi...
For anyone else coming across this, I was only able to get this to work using the account user and password configured during server creation (aka: SA) / comments
For anyone else coming across this, I was only able to get this to work using the account user and password configured during server creation (aka: SA)
Trying this same thing... Are you connecting to the Azure SQL DB using a contained user or did you need to create a login on Master and create a user for that login on the Azure DB? If the latter, what permissions does this login need? Hopefully this is not limited to only using the SA (like) account that was used during server creation.... / comments
Trying this same thing... Are you connecting to the Azure SQL DB using a contained user or did you need to create a login on Master and create a user for that login on the Azure DB?If the latter, w...
2.5 years later, this is still a problem. The issue is the MFA. The token expires and a new one has to be acquired. I believe the default is 1 hour. SSMS handles this automatically, but SQL Prompt does not. Restarting SSMS causes SQL Prompt to restart and acquire the new token. Not a workable solution. / comments
2.5 years later, this is still a problem. The issue is the MFA. The token expires and a new one has to be acquired. I believe the default is 1 hour. SSMS handles this automatically, but SQL Pr...