Default catalog (zone) and schema, plus an audit-log identifier for the application.
Database=<zone>;Schema=<schema>;ApplicationName=<label>## Database (Catalog) and Schema `Database=` (alias `Catalog=`) sets the default zone used when a SQL statement omits the leading catalog qualifier. `Schema=` sets the default schema within that zone. With both set, the statement `SELECT * FROM orders` resolves to `<Database>.<Schema>.orders` without the application having to fully qualify the name. These are convenience defaults, not hard scopes. A statement that fully qualifies its tables (`SELECT * FROM other_zone.other_schema.table`) reaches across the defaults; the values only fill in when the qualifier is missing. ## ApplicationName The driver constructs a User-Agent header for every HTTP request: ``` User-Agent: delta-forge-odbc/<version> (<os>; <arch>) <ApplicationName> ``` Where `<ApplicationName>` is whatever was passed in the connection string, or the default if not set. The engine logs this header on every audit event, which makes downstream attribution far easier than parsing the executable name. Good values to set: - The product short-name and a workload tag: `tableau-server-prod`, `powerbi-refresh-finance`, `dbt-staging-customer`. - A free-text tag identifying the team: `team-finance-etl`. - An incident-tracking ID when running an ad-hoc investigation: `incident-12345`. The value is unstructured; do not parse it on the engine side. Treat it as a label, not as a schema field. ## Case sensitivity Delta Forge object names are case-preserving and stored verbatim. `Database=Analytics` and `Database=analytics` are different zones if the deployment created them with different cases. The convention across the project is lowercase / snake_case for everything; if you stick to that you will not hit a case-mismatch bug.
| Name | Type | Description |
|---|---|---|
Database | Default zone (catalog) used when SQL omits the catalog qualifier. Aliases: `Catalog`. Equivalent to running `USE ZONE <name>` on every connect. | |
Schema | Default schema. Equivalent to running `USE SCHEMA <name>` on every connect. Catalog and schema names are case-preserving; supply them in the case used at object creation. | |
ApplicationName | Suffix appended to the User-Agent the engine sees in audit logs. Useful for distinguishing 'Power BI scheduled refresh' from 'Power BI Desktop' from 'dbt' in observability dashboards. |
# Default to the analytics zone and schema
Database=analytics;Schema=marts# Identify a scheduled job in audit logs
ApplicationName=etl-nightly-customer-load# Cross-vocabulary aliases
Catalog=analytics;SCHEMA=marts