How to Use Database Profiles
Step-by-step guide for creating database profiles, selecting a vendor, reviewing type mappings, adjusting naming conventions, and assigning profiles to ERD views.
Database profiles control how the data model's abstract types are mapped to concrete database column types. Each profile targets a specific database vendor and includes pre-populated type mappings, naming conventions, and constraint syntax. ERD views reference a profile to render tables with vendor-specific types.
Create a Database Profile
Supported Vendors
Assign a Profile to an ERD View
Multiple Profiles for One Model
A single model supports multiple database profiles simultaneously. This is useful when the same data model needs to produce ERD views for different environments:
- A PostgreSQL profile for the production database.
- A SQL Server profile for the analytics data warehouse.
- A SQLite profile for local development and testing.
Each ERD view references exactly one profile. Create separate views for each target database.