First Due's Open Database Connection (ODBC) provides users with direct access to their department's data through a PostgreSQL data warehouse hosted on AWS. This connection enables departments to analyze, extract, and integrate their First Due data with external analytics applications, business intelligence tools, and custom reporting solutions for enhanced operational insights.
The ODBC connection serves as a bridge between your local environment and First Due's cloud-based data warehouse, which contains approximately 100 tables organizing data from nearly all First Due modules into analytics-ready datasets. This warehouse is not a direct replication of the production database but reflects current production data with regular refresh cycles. The connection is particularly valuable for departments seeking advanced analytics capabilities, custom reporting solutions, or integration with existing business intelligence platforms.
Submit a support ticket or contact your Implementation/Client Success Manager to request ODBC connection credentials and setup information.
Download and install the appropriate PostgreSQL ODBC driver for your operating system from the official PostgreSQL website.
Verify the connection is working properly by testing the data source configuration before proceeding with your analytics application setup.
Configure your chosen analytics tool, BI platform, or database client to use the established ODBC connection for data access.
Data Refresh Understanding:
Time Zone Considerations:
Query Optimization:
Schema Management:
Q: What is ODBC? A:First Due's open database connection allows users to access their data through applications designed to analyze or extract their data. First Due's ODBC is a connection to a PostgreSQL data warehouse hosted on AWS.
Q: How do I get description information for ID reference fields?
A: Some foreign keys reference information not included in the warehouse. Contact support to request lookup tables for specific ID fields you need decoded.
Q: My timestamps appear incorrect - how do I fix this?
A: Most timestamps are stored in UTC. Convert these fields to your local time zone, or look for corresponding "_local" labeled fields where available.
Q: How will I know about changes to the warehouse structure?
A: Schema updates and changes are communicated through product release notes, with advance email notifications sent to department contacts when possible.
(You can sign up for a ODBC Notification list for schema changes by filling out this form: ODBC Schema Change Notifications)
Q: Who can help with specific field or table questions?
A: Submit a support ticket or contact your Implementation/Client Success Manager to connect with a reporting product specialist.
Q: Can I use this connection as a backup solution?
A: No, the warehouse is not designed as a backup solution. It reflects production data but should not be relied upon for backup purposes.
Q: What is ODBC?
A: First Due's open database connection allows users to access their data through applications designed to analyze or extract their data. First Due's ODBC is a connection to a PostgreSQL data warehouse hosted on AWS.
Q: How does the connection work?
A: Data is hosted on our server, and the ODBC connection allows you to access this data from your local environment. Data is not being "pushed" from the ODBC.
Q: What data is in the warehouse?
A: The warehouse is comprised of about 100 tables which organize data across almost all First Due modules into analytics-ready datasets. The tables contain a mix of raw data and pre-computed columns for enhanced usability. If a module is not purchased, there will be no data in the associated tables.
Q: How does data flow from the database to the warehouse?
A: The warehouse is not a replication of our production database but reflects the data that is stored in our production database. The warehouse will update alongside updates in production and does not necessarily serve as a backup.
Q: How recent is the data?
A: We offer refresh rates as frequently as 4 times a day, but the most common refresh rate is once a day.
Q: What is ODBC commonly used for?
A: Many users will use the ODBC connection for running queries or for connections to analytics applications or BI tools. Users "pull" the data from the ODBC to host in their own environment.
Q: How will updates be communicated?
A: Product release notes include enhancements to the back-end tables. While we try to avoid high risk changes, updates to the schema or data types sometimes become necessary. We try to give advance notice as soon as possible of these changes, with these notices being sent to the fire department contact via email.
Q: Why are timestamp fields not stored in local time zone?
A: Most timestamp fields in the warehouse are stored in UTC, which means that you must convert the fields to the local time zone to read the timestamps in the local time zone. The few fields that are stored in local time zone will be labelled as [field name]_local.
Q: Why are there ID reference fields stored without a matching reference table?
A: There are some foreign keys designed for joins that will not match another table in the warehouse for description information. An example of this is event type, by which you have access to the ID but not the name of the event type itself. We can provide lookup tables for this information by request.
Q: Where should I direct questions about the fields and tables in the warehouse?
A: Submit a ticket to support: Submit a Support Ticket or speak with your Client Success or Implementation Manager to be connected with a reporting product specialist.