The following table maps the various providers to the operating system and RDBMS versions against which they have been tested (T). The provider requires that an Oracle client is installed in order to communicate with the Oracle database. It is your choice to install just the Oracle client or the client and server combined. Connection to a remote SQL Server database is done through the standard ODBC component that is installed with the Windows operating system so that installing a SQL Server client is not a necessity. The FDO API provides user and data store management for both the Oracle and SQL Server providers. You may, nevertheless, wish to install a SQL server client.
FDO and its Providers run on the Windows Vista operating system. However, Autodesk cannot guarantee that the underlying file or database that an FDO Provider is connecting to is Vista compatible (except for the Autodesk Spatial Data File format, SDF). Please consult the file or database vendor to verify Vista compatibility.
| WXP=Windows XP Pro; W2K=Windows 2000 Pro; W2K3=Windows 2003 Server | ||||||
|---|---|---|---|---|---|---|
| Provider | WXP | W2K | W2K3 | Linux | RDBMS | Notes |
| Oracle | T | T | T | T | Oracle 10gR2 certified; Oracle 10gR1 and Oracle 9i are NOT certified (supported but not tested). Oracle Workspace Manager (OWM) is supported up to but NOT including version 10.2.0.4. | 1 |
| SQL Server | T | T | T | n/a | SQL Server 2000 SP 4 and SQL Server 2005 are certified | |
| Raster | T | T | T | T | TIFF, MrSID, PNG, JPEG, JPG2K, DEM, and ECW tested. | |
- In previous releases the use of the Oracle Workspace Manager for versioning (locking and long transactions) was enabled by default. In the current release the OWM is disabled by default and so, therefore, is support for versioning. How to reenable versioning is described in the Oracle appendix in the FDO Developers Guide.