Choosing Your Data Provider

Your choice of data provider may depend on several things:

The strengths and weaknesses of each supported data provider type regarding the above factors is discussed in detail in Data Provider Implementation Notes.

Provider-Independent Text Files allow you easily share data among multiple workgroups or organizations, however we recommend that all WRDB users within the same organization use the same data provider if possible.

For example, Georgia EPD has a number water quality modelers and who independently compile data for water quality model input using WRDB. Although they do not typically share data, all have chosen to use the SQLite data provider and store their data on their local hard disk. They are responsible for backing up their data files, and can easily take entire WRDB projects home by just copying a single database file. When the project is complete, they will create provider-independent archives of their data which will be stored on disk.

However, other WRDB users at EPD are required to compile all laboratory data and make it available throughout the organization. These data are stored on an enterprise Oracle server accessible to only EPD personnel. The Oracle DBA makes nightly backups, but the Project manager is also able to make off-site backups as previously described.

In another application, an EPD consultant is hosting a MySQL database server at a central location for a large project being worked on by teams scattered throughout the State. MySQL is free, has very good performance, and meets the project requirements well.

All data providers described here are fully supported by WRDB, however practically speaking, during development some providers have been used more than others. The order of providers relative to our experience is: