SSMS Object Explorer doesn't show any of my databases

Hi!

First of all, don't get discouraged! SQL Server can be confusing when you're starting out, especially when you have multiple instances installed on the same machine. We've all been there, and I'm sure one day you'll look back at this and have a good story to tell :)

I suspect one of two things might have happened.

1. You might be connecting to a different SQL Server instance.

Since you mentioned installing a newer SQL Server version and initially connecting to the older one, I'd start by checking how many SQL Server instances you actually have installed.

Open SQL Server Configuration Manager and navigate to SQL Server Services.
CMD -> Run -> SQLServerManager17.msc (for SQL Server 2025). Other version you can check here:

https://learn.microsoft.com/en-us/sql/tools/configuration-manager/sql-server-configuration-manager?view=sql-server-ver17 

Then you should see entries such as:

- SQL Server (MSSQLSERVER) – the default instance

- SQL Server (YourInstanceName) – another named instance

For example my Configuration Manager,  show me only one instance: 

Check how many SQL Server Database Engine services are listed and whether they're running. Each instance is independent and maintains its own databases. Just because the MDF and LDF files exist somewhere on your disk doesn't mean they're attached to the instance you're currently connected to.

Once you identify your instances, try connecting to each one in SSMS and run:

SELECT
SERVERPROPERTY('ServerName') AS ServerName,
SERVERPROPERTY('InstanceName') AS InstanceName,
SERVERPROPERTY('ProductVersion') AS ProductVersion;

SELECT name, state_desc
FROM sys.databases;

This should help us identify which instance you're connected to and whether your databases are registered there.

2. Could you have accidentally detached your databases?

Since you mentioned trying several things while troubleshooting, do you remember using Tasks > Detach in SSMS or executing `sp_detach_db`? Detaching a database removes it from the SQL Server instance but leaves the MDF and LDF files on disk. That would explain why the database files still exist but the databases are no longer visible in SSMS. If that's what happened, we may be able to attach them again. However, let's confirm the situation before making any more changes.

Microsoft documentation:

https://learn.microsoft.com/sql/relational-databases/databases/database-detach-and-attach-sql-server 

One useful SSMS feature for the future: Registered Servers. Since you're working with multiple SQL Server instances, I'd also recommend exploring the Registered Servers feature in SSMS.

You can open it using View > Registered Servers or Ctrl+Alt+G.

It allows you to register your SQL Server instances, give them meaningful names, organize them into groups, and easily connect to the correct instance. For example, you could register your instances as "SQL Server 2022 - Local" and "SQL Server 2025 - Local" to avoid accidentally working on the wrong one.

Documentation:

https://learn.microsoft.com/ssms/register-servers/create-a-new-registered-server-sql-server-management-studio 

And a few friendly suggestions:

- Always take a backup before making significant changes to your databases

- Double-check which instance you're connected to before executing administrative commands

- Avoid manually deleting or moving database files while troubleshooting

- Try changing one thing at a time. It's much easier to identify what went wrong that way

For now, I wouldn't uninstall, delete, or recreate anything. Your database files may still be perfectly fine, and we first need to understand what's happened.

And don't give up! Every experienced DBA has a few stories about mistakes made while learning. The difference is that eventually those mistakes become lessons, and sometimes even funny stories we tell other people :)