WARNING

DB OPTIMIZER 17.0.1 AND LATER CANNOT USE ANY WORKSPACES PRODUCED BY PREVIOUS DBO VERSIONS, NOR CAN IT USE ANY FILES CREATED BY THOSE OLDER WORKSPACES.

Upgrade Notes

  • DB Optimizer should be installed in a different directory than previous versions of DB Optimizer. If DB Optimizer is installed in the same directory, the following error will result in at application start up: "Unable to read workbench state. Workbench UI layout will be reset.
  • If a previous version is already installed on your machine, either change the default Workspace or delete all files from the Workspace directory. The Workspace directory location appears whenever you start Optimizer, and can be redefined from this dialog box. If the same Workspace is indicated for the new version as was indicated previously, the following error will result: "Cannot restore workbench layout".
  • If DB Optimizer is already running, you can also modify the Workspace directory by choosing File > Switch Workspace > Other from the Main Menu.
  • We strongly suggest selecting a new workspace when upgrading from a previous version of DB Optimizer.
  • Saved profiling and tuning session files (.oar) created using previous versions of DB Optimizer are not compatible with current versions. You can however have more than one version of DB Optimizer installed on the same system. To read old .oar files, run the older version of DB Optimizer.

Known Issues

The SQL Server sqlvariant data type is not currently supported by the Microsoft JDBC driver. If a query is used to retrieve data from a table that contains a column of the sqlvariant data type, an exception will occur. There are two workarounds to fix this issue:

  • Use CAST to type cast the sqlvariant columns to the data type you want.

Or

  • Use the jTDS driver to connect.