If you have a table editor license, DivePort can define tables and build the required xml files that you can use to develop an application. By default, these tables work with flat text files to store your data. As an administrator, you can point these tables to a database structure. If you anticipate more than 10,000 rows in a table, DI recommends that you use a database.
If you are building your own application using the table editor, you can use a database such as PostgreSQL or SQL Server.
If you plan to use a database with DivePort, you must incorporate additional steps into any backup schemes in place, including creating and scheduling a job to copy database table contents to flat files so that they can be archived with the other DI files. You must also plan and prepare steps to restore your database tables, such as clear and reload with the archived data. Consider using a command line or GUI option for this.
Use an ODBC interface for interoperability. DivePort can access data in your database through an ODBC interface.
TIP: Use consistent data types in your DivePort, ODBC, and database table to ensure accurate results.