Exporting to ODBC

You can export model component data to an ODBC (Open Database Connectivity) database.

The exported data can include project parameters that have been assigned to one or more element categories in the project. For each element category, Revit exports a database table for model types and another table for model instances.

Examples

• Architecture: Revit creates a table listing all door types and another table listing all door instances.
• Structural engineering: Revit creates a table listing all structural column types and another table listing all structural column instances.
• Systems engineering:Revit creates a table listing all lighting fixtures and another table listing all lighting fixture instances.

ODBC export uses metric units only. If a project uses Imperial units, Revit converts all measurements to metric units before exporting to ODBC. When you use data from the resulting database, remember that the measurements reflect metric units. Use a database function to convert the measurements back to Imperial units if necessary.

Using ODBC, Revit creates tables for the following elements:

• Model Objects: Types and Instances
• Levels and Rooms: Instances only
• Key Schedules
• Assembly Codes: A single table containing assembly code data for the entire project

ODBC export creates specific relationships between tables in the database using primary keys and reference values. See About Table Relationships Within the Database.

Revit can export to the same database multiple times. When exporting to an empty database, Revit creates new tables. When you export a project to a populated database, Revit updates table information to match the project. This allows you to customize the database and re-export data as the project changes.

Attention: Do not export different projects to the same database. Use a unique database for each project.