Convert SDF to MDB

A SQL Server Compact database may need conversion when an application, colleague, or older Windows system requires a Microsoft Access database. The conversion copies the SDF tables and records into an MDB file; changing .sdf to .mdb does not change the database format.

What the SDF format is

In the Databases category, SDF normally identifies a SQL Server Compact database, also called SQL CE. It is an embedded, file-based relational database used by older .NET applications, desktop utilities, mobile software, and other programs that need local storage without a database server.

An SDF file can contain tables, columns, indexes, relationships, constraints, and data. SQL Server Compact 3.5 and 4.0 are common versions. Password protection or encryption can prevent conversion unless the correct credentials and compatible SQL CE provider are available.

What the MDB format is

MDB is the Microsoft Access database format used natively through Access 2003 and supported for backward compatibility by later Access versions. It is suitable when the destination system requires Jet-compatible tables or an older Windows application accepts only MDB files.

Access can provide a desktop interface for editing tables and can add queries, forms, reports, and macros. These Access objects are not present in an SDF file and are not created automatically by a data migration. MDB has a 2 GB maximum file size, excluding linked-table data; Jet and older Access applications may also impose narrower limits on field types, names, indexes, and expressions.

Convert with a database migration utility

A dedicated Windows utility such as Full Convert Enterprise is usually the most direct option if its installed version lists SQL Server Compact as a source and Microsoft Access MDB as a destination. Product editions and current provider support vary, so verify both formats before purchasing or starting the migration.

1. Back up source.sdf and close applications that use it.
2. Install the converter and create a new project or conversion job.
3. Choose SQL Server Compact as the source, select source.sdf, and provide the password or connection settings if required.
4. Choose Microsoft Access, Access MDB, or the equivalent Jet destination and set a new output path such as converted.mdb.
5. Review the mapping. Preserve primary keys, identity or AutoNumber behavior, indexes, nullable settings, and relationships where the utility supports them.
6. Run the job, open the resulting MDB in Access, and compare row counts, keys, dates, Boolean values, Unicode text, binary fields, indexes, and relationships with the source.

Use SQL Server Compact Toolbox for a manual migration

SQL Server Compact Toolbox can inspect an SDF file and script its schema and data, but it is a legacy tool and requires a compatible SQL Server Compact provider. This method is useful when a commercial converter cannot open the particular SDF version or when every schema change must be reviewed.

1. Open source.sdf in SQL Server Compact Toolbox and run its database scripting command, commonly named Script Database Schema and Data.
2. Create an empty database in Access with File → New → Blank database, saving it as converted.mdb.
3. Adapt the generated SQL to Access SQL. SQL Server Compact and Jet use different data types, identity syntax, functions, reserved words, and constraint syntax.
4. Run the adjusted definitions in Access, using Create → Query Design → SQL View where appropriate, or recreate the tables manually.
5. Load the exported rows into the new tables, then recreate primary keys, indexes, and relationships and verify identity values.

For simple tables, CSV can serve as an intermediate format, but it does not preserve relationships, indexes, constraints, data types, or binary values. Use a structured script or migration utility when those elements matter.

Compatibility and online-conversion limits

The migration generally transfers relational tables and data, not the behavior of the original application. SQL Server Compact-specific queries, triggers, calculated expressions, encryption settings, identity rules, and unsupported data types may need manual replacement. Access does not provide a universal native import path for every SQL Server Compact release, and installing an old SQL CE provider does not by itself make Access able to open an SDF file.

Check decimal precision, long text, timestamps, null values, binary columns, Unicode characters, reserved identifiers, and identity values after conversion. Test application queries and joins against the MDB. If the result would exceed MDB's 2 GB limit, divide the data into linked tables or use ACCDB if the receiving software supports it.

Reputable general-purpose online converters rarely advertise reliable SQL Server Compact SDF-to-MDB support. Avoid uploading databases containing personal, proprietary, or regulated data; online services may also discard relationships and provider-specific objects without exposing detailed mapping controls. Use an offline converter for this conversion, and only use an online service after confirming its exact SQL CE and MDB support and its data-retention policy.