Comments
2 comments
-
Hey Neil,
It was good working with you and I am glad you are up and running now!
For everyone who is reading this (and using Auditing in Azure), you can edit either the security-enabled connection string or the security-enabled access settings to allow the tool to connect properly.
Here is an excellent article on this https://azure.microsoft.com/en-us/docum ... t-started/
If you have any issues with this please let me know!
Warmly,
Andrew
Product Support Engineer
Red Gate -
The more helpful document was actually this one:
https://azure.microsoft.com/en-us/documentation/articles/sql-database-auditing-and-dynamic-data-masking-downlevel-clients/
Which specifically mentions using this:
Original server FQDN in the connection string: <server name>.database.windows.net
Modified server FQDN in the connection string: <server name>.database.secure.windows.net
which is all that wass needed to solve the issue.
Add comment
Please sign in to leave a comment.
Cannot open database '' on server 'xmyserverx' requested by the login. Access to the database is only allowed using a security-enabled connection string. Changed database to 'master'.
Any ideas would be appreciated as I will shortly have upwards of 30 databases to run these scripts against and I really don't want to run each one manually if I can help it.