Cannot open mdf file in Microsoft SQL Server Management Studio Express 2005

[colbysloan]

I had Microsoft SQL Server Express 2005 installed already. I just installed the Microsoft SQL Server Management Studio Express 2005 and tried to open my mdf file. I get an error message that says:

 

There is no editor available for 'C:\Inetpub\wwwroot\intranet\app_data\intranet.mdf).

Make sure the application for the file type (.mdf) is installed.

 

Did I do something wrong? I just clicked through the defaults in the Management Studio Express install.

 

How can I get this to work?

[Guest]

different profile pic pls.

[0ld_Chicken]

by not putting a picture of a butt as your profile pic

 

 

How can I get this to work?

[lol1290]

after 8 minutes... profile pic changed

[qismafaraj]

Try this one guide...

 

1. First Shutdown SQL Server

2. Then move the current database file/rename (do not touch the .ldf)

3. After rename/move db, restart SQL Server

4. Create a new database with same name and log file and location also same

5. Stop SQL Server

 

Last one variant provided for completely crashed .mdf and .ldf files, when other ways can’t handle the situation https://repairsql.recoverytoolbox.com/ Recovery Toolbox for SQL Server - free demo version of this tool, if any variant doesn’t seem effective

[LukeTim]

Why do you want to "open" your mdf file? You don't open the mdf file with SQL Server Management Studio.

Management Studio connects to the Database Engine (which runs as a Windows Service) and allows you to modify the Database using the Database Engine.

Open Management Studio. Hit connect and type "localhost" into the server name field, and use your login details.

I have not used 2005 Express, but it cannot be too different from 2008.

[BiggHertz]

@LukeTim is correct.

 

You do not directly open an MDF file. To gain visibility or view into it's contents, simply use SSMS to connect to the SQL Engine. If it is a local and default instance, "localhost" in the ServerName field, and ServerType is set as "Database Engine", with appropriate credentials is used you shouldn't have issues connecting. However, if there is more than a single instance installed or the default listening port of 1433 has been changed, you will need to modify the ServerName field. 

 

Be sure to verify, that TCP/IP Protocol has been enabled in SQL Configuration Manager and if connecting from a remote PC, that the appropriate firewall exceptions have been made.

 

Hope that helps!

 

-Jason