Hey there, let's walk through the most reliable ways to pull this info from your .MDF file. I've used these methods dozens of times when troubleshooting old databases, so they're tried and true.

Method 1: Attach the MDF to SQL Server (Full Details) #

This is the best approach because it gives you everything—version, update level, and edition—instead of just a partial number. Here's the step-by-step:

1. Fire up SQL Server Management Studio (SSMS) and connect to any compatible SQL Server instance (important: you can't attach a higher-version MDF to an older SQL Server; if you get an error later, that's probably why).
2. Right-click the Databases node in Object Explorer → hit Attach....
3. Click Add in the Attach Databases window, then browse to your .MDF file. If you have the matching .LDF log file, it'll show up automatically. If not, SSMS will try to rebuild the log file (this works for most cases, but keep a backup just in case).
4. Once the database is attached, run this T-SQL query in a new query tab:

SELECT
  SERVERPROPERTY('ProductVersion') AS [Product Version],
  SERVERPROPERTY('ProductLevel') AS [Update Level],
  SERVERPROPERTY('Edition') AS [SQL Server Edition];

Let's break down the results:

• Product Version: The full version string (e.g., 15.0.2000.5 = SQL Server 2019). The first two numbers usually tell you the major version.
• Update Level: This tells you if it's the initial release (RTM), a Service Pack (SP1, SP2), or a Cumulative Update (CU1, CU12, etc.).
• Edition: The type of SQL Server used (Enterprise, Standard, Express, Developer, etc.).

Method 2: Check the MDF File Header (No Attachment Required) #

If you can't attach the file right now (maybe you don't have a compatible SQL Server handy), you can still get the base version from the MDF's file header. Here's how:

1. Open SSMS, connect to any SQL Server instance, and run this to enable console output for DBCC commands:

DBCC TRACEON(3604);

2. Run the DBCC PAGE command, replacing the file path with your MDF's location:

DBCC PAGE('C:\Path\To\Your\Database.mdf', 1, 0, 3);

3. Scan the output for the dbi_version field. This number maps directly to the major SQL Server version:
   • 70 = SQL Server 2000
   • 80 = SQL Server 2005
   • 90 = SQL Server 2008
   • 100 = SQL Server 2008 R2
   • 110 = SQL Server 2012
   • 120 = SQL Server 2014
   • 130 = SQL Server 2016
   • 140 = SQL Server 2017
   • 150 = SQL Server 2019
   • 160 = SQL Server 2022

⚠️ Heads up: This only gives you the major version—you won't get the update level or edition here. For those, you'll need to attach the file to a compatible SQL Server.

Method 3: SQL Server Setup Discovery Report (Compatibility Checks) #

If you're not sure which SQL Server version can handle your MDF, or want to list all local SQL Server installs with their full details, generate a discovery report:

1. Open Command Prompt as Administrator.
2. Navigate to the Setup Bootstrap folder of your SQL Server installation (example path: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log—replace 150 with the version folder for your install if you have multiple).
3. Run this command:

Setup.exe /Action=RunDiscovery

4. The report will open in your browser, showing every local SQL Server instance with its full version, edition, and update level. Match this with the dbi_version from Method 2 to find a compatible instance to attach your MDF to.

Pro Tips #

• Always make a copy of your MDF file before messing with it—data loss is rare, but better safe than sorry.
• If attaching fails with a "version mismatch" error, use Method 2 to check the dbi_version and upgrade your SQL Server to a version that supports it.

内容的提问来源于stack exchange，提问作者student