Comments
8 comments
-
I think we solved this this morning? It was an incorrect SA password ultimately.
-
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.... -
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)
-
Hi
we're considering going down this route for our sql monitor database, apart from the sa issue did you have any other issues around connecting to monitored instances? we've got a hybrid estate of sql servers at the moment -
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.
-
That is correct, due to the auto detection I'm afraid. Suspending the database however is something I think we've just overlooked, as you can suspend individual instances. We've talked about treating Azure sql databases in the same way as an instance so this might change in the future, I can't promise anything though.
-
J
-
Hi!
I managed to connect to Azure SQL Database with a user that is not sa. The trick is to tick the two Checkboxes in Connection Properties:
redgate: Maybe it would be a good idea to write all this into the part of the documentation where you describe how to setup SQL Monitor with Azure SQL Database. I think the descripton is a little bit "brief".
Thank you and have a nice day
Frank Geisler
Microsoft MVP
Friend of Redgate
Add comment
Please sign in to leave a comment.
application_name Redgate Installer