Sql-server – Can’t see second azure sql database in SSMS object explorer

azuresql serverssms

I have created a second database on my existing Azure SQL server. The first database works fine and I can see it using SSMS.

I cannot see the second database in the object explorer. Autocomplete detects that it exists however.

Any suggestions?

Best Answer

So for me, it turned out that when I was connecting using SSMS, I had set the database to connect to as my first database by accident - meaning that was all I could see.

On connect, go to Options, then check the database you're connecting to. If you're using multiple users to connect to that server like I was, my admin user ended up also being forced to connect to a single database instead of < default >.

Related Solutions

Sql-server – What permissions might be missing on error 229 from ‘tables’ node on SSMS object explorer

Might not be the same thing but I was getting that error today.

Turned out that in my haste to grant a user full access to a database I ticked all the boxes under role members including db_denydatareader, db_denydatawriter.

Can’t connect to MS SQL Server database using SSMS

It sounds like your host has done the following:

REVOKE VIEW ANY DATABASE FROM public

...and this prevents browsing the database list in SSMS, although it doesn't stop you seeing that list using other techniques, or connecting to your database in a query window.

I think the only thing you can do is ask them to change it back, or at least to verify that that's indeed what they did.

Best Answer

Related Solutions

Sql-server – What permissions might be missing on error 229 from ‘tables’ node on SSMS object explorer

Can’t connect to MS SQL Server database using SSMS

Related Topic