This build of DB Optimizer includes many fixed issues, including the following updates.
17.0.4 Fixed issues
There are no customer-reported issues fixed in the DB Optimizer 17.0.4 release.
17.0.3 Fixed issues
| Issue # | Description | DBMS |
|---|---|---|
| OPT-5269 | Trying to view "Using DB Optimizer" web page causes an error | All |
| OPT-5270 | Optimizer not collecting "sql_statement" information | Sybase ASE |
| OPT-5273 | Data source name cannot exceed 30 characters in CM and DBO | All |
| OPT-5274 | Install/Config error: Driver not configured for integrated authentication | SQL Server |
17.0.2 Fixed issues
There are no customer-reported issues fixed in the DB Optimizer 17.0.2 release.
17.0.1 Fixed issues
| Issue # | Description | DBMS |
|---|---|---|
| OPT-5017 | SQL Editor problems do not appear in Problems view | SQL Server |
| OPT-5082 | Error log does not show errors reported by tuning session | All |
| OPT-5086 | SQL tuning session cost color preference not working | All |
| OPT-5087 | SQL tuning session cost color preference also applied to elapsed time | All |
| OPT-5088 | SQL tuning session stops if the elapsed time is longer than the original | All |
| OPT-5097 | SQL tuning session offers obvious selection criteria for picking winner | All |
| OPT-5098 | SQL tuning session should highlight # winners found and % improvement | All |
| OPT-5103 | DBO needs a priv grant wizard like DBArtisan's capacity analyst | Oracle |
| OPT-5106 | Saving a tuning session does not persist/save user selections | All |
| OPT-5121 | "Tables/Views/Synonyms" are not getting resolved in SQL Server and Sybase when it exists in schema other than DBO | SQL Server, Sybase |
| OPT-5122 | Sybase: table name is getting resolved but not executed | Sybase |