the latest version

Database Integration

The Enterprise edition of Windographer works with any database server that supports stored procedures to allow multiple users to interact with centrally-stored wind resource data. Windographer communicates with the database via stored procedures, meaning it does not need to know anything about the names or structures of the tables in which the database stores the data. The database administrator writes the stored procedures such that they query the data and format them into record sets in the format that Windographer requires.

Windographer can read from and write to the database not just the numerical data, but also flags, flagged segments, and data set history indicating who did what and when.


Windographer expects the contents of the database to be organized into “data sets”. A data set is the information needed to analyze wind resource data for a particular location, including:

  • time series data, such as speed, direction, and temperature measurements
  • metadata, such as calibration constants, data column types, and measurement heights
  • Windographer-specific data, such as flags, flagged segments, and the history of changes

At a minimum, Windographer requires the time series data and certain metadata to perform meaningful wind resource analysis. While database does not necessarily have to store the Windographer-specific data to work with Windographer, doing so dramatically enhances Windographer's usefulness in working with the database. For instance, if the database stores data on flags and flag status, multiple users can flag for possible errors or quality problems, and all see each other's work.


To allow communication with Windographer, a database must satisfy the requirements described in this document:

Windographer Database Specifications

Windographer Database Creator

If your organization has not already created a database system, you may want to consider the Windographer Database Creator, a utility program that builds a database structure and writes all the stored procedures necessary to communicate with Windographer.

Database Administration

Windographer does not attempt to implement its own security for the database. Rather, it builds on the security features that the database server software offers. Typically individual users will have their own IDs that they use to connect to the database server. Windographer uses these IDs to track changes.

Windographer also allows the database administrator to specify permissions (on a per-user basis) so that it can warn users if they about to make a change that they won't be able to save to the database. This way, users don't get trapped into doing hours of analysis, only to find out, when they finally attempt to store the data, that they don't have permissions to make the changes.

Supported Database Platforms

Most customers currently using the Enterprise edition of Windographer store their data in Microsoft SQL Server databases, so that is the platform we have tested most thoroughly. We have also done some testing against Oracle and MySQL. For other database platforms, please contact us to inquire about compatibility.

Benefits of Storing Wind Resource Data in a Database

A database provides a central location for your data, so you never have to look for a data file, or wonder whether you have the most recent revision. Centralization helps enforce consistency, avoid duplication of data, and maintain security. It is an open system that allows you to access the data through channels other than Windographer, for example to run your own automated quality control or to allow customized reporting. It also provides a robust means of backing up your data because the database can be backed up regularly.