Azure / SQL Server / Cannot open user default database (Login failed)
Posted by Barac in Azure, SQL Server on Oct 26th, 2017 | 6 commentsYou want to create a new login on Azure Logical SQL Server using your Azure Admin account.
To do that you must be connected to the master database on SQL Azure with the administrative login.
After that, you need to create new DB user for that login (db_owner in this example). To be able to do that you must be connected as an admin to the database where you want to create that user.
Now, if you try to connect to that db using SSMS you need to specify default DB for that user.
Since you cannot set the default database property for the login, default DB will always be [master] database.
If you do not change DB before connection, and user do not have rights to access master DB, you can face following error
The server principal “azure_db_user” is not able to access the database “master” under the current security context.
Cannot open user default database. Login failed.
Login failed for user ‘azure_db_user’. (.Net SqlClient Data Provider)
You can also use connection string from azure portal specifying Initial Catalog (DB Name)
Similar Posts:
- Azure / SQL Server / Azure DB / Add Logins, Users, Permissions
- Azure / PowerShell / Deploy Azure SQL database DR environment (PaaS) using PowerShell
- Azure / SQL Server / Azure SQL Database Disaster Recovery / Orphaned Users / Different SIDs
- Azure / SQL Server / Rename an Azure SQL database
- Azure / SQL Server / Create DB on Azure
6 Responses to “ “Azure / SQL Server / Cannot open user default database (Login failed)”
Leave a Reply
About Me
My name is Zoran, currently living in Auckland, New Zealand. I am a data specialist with more than 15 years of hands-on experience in database administration and optimisation. I am also, Certified Microsoft Trainer (MCT) and Microsoft Certified Solutions Expert (MCSE) with a Master‘s degree in Information Technology. Sharing knowledge and contributing to the SQL Server community is my passion. I am also an organiser of the Auckland SQL User Meetup Group. As well I am active blogger and speaker at different SQL events such as SQL Saturdays, Meetups etc.
read moreAuckland SQL Group
MSDN PROFILE
SQL SERVER UPDATES
- Microsoft SQL Server 2022 Updates / Release Candidate (RC 1) Evaluation Edition (16.0.950.9)
- Microsoft SQL Server 2019 Updates / BETA (15.0.1000.34) / RTM (15.0.2000.5)
- Microsoft SQL Server 2017 Updates / RTM (14.0.1000.169)
- Microsoft SQL Server 2016 Updates / RTM (13.0.1601.5) / SP1 (13.0.4001.0 or 13.1.4001.0) / SP2 (13.0.5026.0 or 13.2.5026.0) / SP3 (13.0.6300.2 or 13.3.6300.2)
- Microsoft SQL Server 2014 Updates / RTM (12.0.2000.0) / SP1 (12.0.4100.1 or 12.1.4100.1) / SP2 (12.0.5000.0 or 12.2.5000.0) / SP3 (12.0.6024.0 or 12.3.6024.0)
- Microsoft SQL Server 2012 Updates / RTM (11.00.2100) / SP1 (11.0.3000.0 or 11.1.3000.0) / SP2 (11.0.5058.0 or 11.2.5058.0) / SP3 (11.0.6020.0 or 11.3.6020.0) / SP4 (11.0.7001.0 or 11.4.7001.0)
cool thanks
No worries Luis!
Really useful, i got the solution after 2 days from this blog.
Great work..
Thanks Subramani,
I am glad you solved the problem.
Cheers
Dude. This is the best answer on the web. Thank you!
Thanks Hue,
I am glad it worked for you
Cheers