SQL Server 4060 Cannot Open Database

How to fix 4060

General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.

1. 1

   Confirm the database is online

   4060 means authentication succeeded but the database could not be opened. Check its state before anything else.

   SELECT name, state_desc FROM sys.databases WHERE name = 'YourDb';

2. 2

   Verify the login is mapped to a user

   The login needs a database user with CONNECT permission inside the target database.

   USE YourDb;
   SELECT name FROM sys.database_principals WHERE name = 'youruser';

3. 3

   Fix an invalid default database

   If the login's default database is offline or deleted, connections fail before reaching a valid one. Point the default at master.

   !High-impact command - back up first and proceed carefully.

   ALTER LOGIN [youruser] WITH DEFAULT_DATABASE = [master];

4. 4

   Correct the connection string

   Make sure the Database or Initial Catalog value names a database the login is actually allowed to open.

Technical Background

Common Causes

• The database name in the connection string is incorrect
• The database is offline or in emergency mode
• The user does not have permission to access the specific database

Typical Scenarios

• Connecting to a restored database before permissions have been remapped
• A database being renamed while applications are still using the old name

What to Know

Checking that the target database is online and accessible is the primary step. In cases of invalid default databases, administrative reconfiguration of the login is required to restore access.

Frequently Asked Questions

Common questions about SQL Server 4060 error